-
Notifications
You must be signed in to change notification settings - Fork 16
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
Minification with source maps fails with current Uglify-JS #59
Comments
@PatTheMav Thanks for reporting this to me! These backward incompatible changes are killing me, because if I fix the CLI parameters in my program then everyone else will complain start to complain who are not yet upgraded to the latest version of UglifyJS ... Also, there are changed / incompatible CLI options between UglifyJS 2 and UglifyJS 3 , those are already causing problems for me. IMHO, the author(s) of UglifyJS shouldn't change CLI options which were there for years. I leave this issue open for now and will deal with it later. When possibly more people upgrade to the new incompatible version of UglifyJS. |
@tssajo - I feel you - maybe parsing the output of |
Hi @tssajo We also have this problem on upgrade UglifyJS. |
I am also getting same error what should be the approach to resolve this. |
In case you're still looking for a solution, I think in v3 you don't have to specify the name of the "mapped" file: I'm not sure about the --source-map-url as I don't need this myself, but this works for me: It generates |
@gregoryforel Thanks, works like a charm. Alas no official update of the Package since I reported this bug.. 😞 |
@ashucg 's fix is now released. Please do not forgot to upgrade to UglifyJS 3 ! I am closing this Issue now. |
Apparently Uglify-JS 2 has changed their command line scheme for source map creation - it breaks with the current version of Minify:
Here's the associated part of the uglify-js documentation:
As I have a daily task that updates my NPM modules, they are kept up2date and as such the version was upgraded automatically.
The text was updated successfully, but these errors were encountered: