-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Production builds failing in ember 3.4.4 | Build Error (UglifyWriter) #49
Comments
Same error here, also reported in ember-cli NPM Log:
here are my variable versions:
|
Hey, I got a fix for this that got my build back up and running! |
We should confirm with the terser folks that this is a known issue... |
Terser is (understandably) waiting for a minimal reproduction terser/terser#120 I have no idea how to produce that. |
Heya! We just ran into this issue today while upgrading our app. Is |
This appears to have been fixed by Terser. I was able to remove the workaround from our config after updating (As a note, we recently discovered that the workaround caused an issue with our app's ability to run in IE11. Updating version and removing the workaround fixed that problem.) |
Awesome, thank you @donaldsonjulia! |
@donaldsonjulia - getting JS heap out of memory error on production build. when we upgrade ember-cli-uglify to 2.1.0 or 3.0.0 |
In my case I got:
The solution was to update |
@edipox I'm glad the dep update has fixed your build, I just updated ember-cli-moment-shim, but we're still having issues, would you mind sharing how you came up with that exact dep? My error is:
Thanks in advance |
@betocantu93 discovering this issue is a bit of an involved process with two possible paths.
Then you can take that file and run it through Last time I ended up going chunk by chunk deleting things from that I haven't found an easier path, maybe someone else has? |
Documenting my journey, I did what @jrjohnson suggested and here are my findings
Thanks both for answering/documenting |
@betocantu93 You saved my day. The only thing is that using |
@EvgenyOrekhov yes, I think I end up doing just that a couple of days later when the build started to fail again, I pinned the Chrome version to a safe one until terser catches up |
Nothing worked for me. I ended up completely removing |
Recently ran into this issue and ended up replacing |
Similar to #35. I'm deploying this APP to heroku using the nodejs heroku buildpack
package.json
Error details:
Workaround
The text was updated successfully, but these errors were encountered: