-
Notifications
You must be signed in to change notification settings - Fork 13
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
UglifyJS issues #6
Comments
fs-extra (and universalify) only support Node 4+ which supports arrow functions just fine. fs-extra uses them as well. We're not going to revert just to support outdated tooling. You need to use the CC: @jprichardson |
@iongion I don't understand why you'd uglify your own code in a server environment. |
@jprichardson any tips on what if the use case is using this package in a electron app after uglifying it ? |
@RyanZim i understand your point of not reverting the code but can we just add a |
The real solution is to use https://www.npmjs.com/package/uglify-es. That said, I'm not opposed to adding |
I am using
fs-extra
which usesuniversalify
, now there is a problem when using uglifyjs as it does not know arrow functions, can you change the module not to use arrow functions ?The scenario is this:
I deploy NodeJS server side apps, bundled in a single file(executing in AWS lambda env).
As you know, webpack usually has an ignore option when transpiling and in the most common cases
node_modules
is what is ignored.Now, after webpack transpiles the code it will post processes it using UglifyJS and there, UglifyJS gets stuck as it cannot minify arrow functions:
The text was updated successfully, but these errors were encountered: