-
-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Older target browsers break runtime #316
Comments
I did some more debugging and here are some off the diffs: Babel plugins:
Disabling App.js:
Vendor:js
|
The actual bug is over in ember-cli/babel-plugin-ember-modules-api-polyfill#64 (which has some breadcrumbs about what is going on). |
Thanks. Let’s keep this issue here open for awhile for others who might run into this. |
ember-cli-babel@7.20.1 was just released, and should fix the underlying issue. https://github.com/babel/ember-cli-babel/releases/tag/v7.20.1 |
When setting target browsers in
targets.js
file like this:Build succeeds but app actually does no run and fails with error:
However when I target browser is set to
Build succeeds and also app runs perfectly on runtime.
This hints like some sort of Babel transforms mess something up but not sure where is it happening. Is it in this repository, in ember-source or some Babel plugin combinations simply break it.
I have an app in production which has Android >= 4.1 target + Babel v7.12.0 but it's no longer upgradeable as whenever some floating dependency gets bumped it breaks and which of the packages cause this is difficult understand.
How to reproduce
Simply create blank addon or app, set target to Android >= 4.1 and it will fail when trying to visit http://localhost:4200
The text was updated successfully, but these errors were encountered: