Remove @glimmer/web-component advice for async methods about glimmer-website HOT 8 CLOSED

Decided to learn some glimmer tonight, started watching the getting started video, ended up here... I agree with @robbiepitts.

from glimmer-website.

@chrishyle --web-component is no longer a hack that works for async/await. We've removed that "feature".

We need to do something about this part of the docs. We now have no good recommendation for getting async/await to work but we're talking about using it.

from glimmer-website.

FWIW, I tried both the --web-component option and installing @glimmer/web-component, but neither "solved" this for me anyways.

@robbiepitts - were you able to successfully get babel-polyfill to work with Glimmer? babel-polyfill internally uses require and just straight-up importing it (as I would in a babel project) does not seem to play well with the @glimmer/application-pipeline stuff which is using only TypeScript (AFAIK) EDIT: It is also using babel inside of rollup-with-dependencies, but it is not invoking it with the "transform-regenerator" plugin.

I'm new to ember-cli, so maybe I'm missing something?

from glimmer-website.

I got it to work by hacking in "transform-regenerator" to the static list in rollup-with-dependencies and adding import 'babel-polyfill/dist/polyfill'; to the top of my index.ts file (note the use of the dist version, to avoid the require issue).

I would take this further, but it looks like people with more experience in this have noticed that the static approach in rollup-with-dependencies.ts is not correct/scalable: glimmerjs/glimmer-application-pipeline#19 removes it entirely. I assume the PR will also move configuration of babel more towards the ember-cli-build.js approach, but there is no description and too many changes for me to dive into it right now.

from glimmer-website.

Also of interest: glimmerjs/glimmer-application-pipeline#83

from glimmer-website.

@robbiepitts @locks I walked through a temporary fix earlier with @rwjblue after running into this problem myself and finding 5+ unsolved issues about it. I can help with one of the following:

• pulling async/await out of the guide entirely #75
• documenting the workaround described in my PR here glimmerjs/glimmer-application-pipeline#108

What do you think?

from glimmer-website.

@jenweber I think I like the idea of pulling async/await out of the guide. I think it is a red herring. I will defer to @locks though since I am not core.

Thanks a bunch for that PR!

from glimmer-website.

Done!

from glimmer-website.