Closed frsechet closed 7 years ago
I believe this error is upstream. in babel or babili itself. We merely invoke those libs. You may want to also open issues there and cross link.
Can you test with the latest version? Many bugs have been fixed in 0.2.0's underlying babili version...
I'm going to clsoe this, as I don't believe this to be a bug here. If anything it should be opened in babili repo.
Hi @rwjblue thanks I'll have a go with the latest version next week. Maybe it has to do with babili, maybe not, it's hard to say, the error is a bit difficult to read...
FWIW, I was having the same issue on our application, and I set babiliOptions
to have mangle: false
as suggested here, but I seem to be unable to actually disable the mangle plugin. The docs for this don't clearly cover how to format the babili options.
@rwjblue @stefanpenner having similar issues on my end as well. Should this be escalated?
This just bit our team as we upgraded to 2.13 and started taking advantage of the new targets feature. We've switched to ember-cli-uglify 2.0.0-beta1 no problem. Definitely an upstream issue.
Hello,
I suddenly had errors (with no specific code change, so I'm guessing a module update broke my build) when using uglify-js, so I switched to babili.
The following happens after several minutes of
ember build -e production
: