You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2021. It is now read-only.
The first app I generated with the --web-component flag was using @glimmer/application-pipeline": "^0.5.2", and the use of async didn't cause any problems at all.
But I realised that the app I generated today (also using the --web-component flag) uses @glimmer/application-pipeline": "^0.6.0-beta.2", and async no longer works. It throws the following error:
Uncaught ReferenceError: regeneratorRuntime is not defined
I'm not sure if this is the right place to file this issue, but as far as I can tell, the only change was the version of @glimmer/application-pipeline.
The text was updated successfully, but these errors were encountered:
We changed things around a bit and now (as of 0.6.x) we emit ES5 code even for web component builds. This means async / await is being transpiled to use regenerator runtime.
Unfortunately, at this time, there is no simple way of adding back the babel polyfills (or just regenerator runtime). I will try to get this fixed today.
Hello :)
The first app I generated with the
--web-component
flag was using@glimmer/application-pipeline": "^0.5.2"
, and the use ofasync
didn't cause any problems at all.But I realised that the app I generated today (also using the
--web-component
flag) uses@glimmer/application-pipeline": "^0.6.0-beta.2"
, andasync
no longer works. It throws the following error:I'm not sure if this is the right place to file this issue, but as far as I can tell, the only change was the version of
@glimmer/application-pipeline
.The text was updated successfully, but these errors were encountered: