Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[jan] Fix calling UglifyJS compressor.
- Loading branch information
Showing
2 changed files
with
5 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4000caa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was fixed?
Only see sourcemap feature lost...
Can you add it again?
4000caa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It creates the source map automatically, those command line arguments don't even exist.
4000caa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't know how...
I'm going to keep my local revert. Thanks
4000caa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW I'm using version 1.3.5 which is the latest stable version. UglifyJS2 has a different interface and should be considered a different backend.
4000caa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is incorrect. Installing via npm, version 2 is explicitly marked as stable/active -- you actually have to add specific version information to the install string to install the old, deprecated/unsupported version 1 edition.
I would agree that the two versions could use a different driver, but this driver was explicitly written for the stable/current package (i.e. version 2).