News for hackers. Stuff that matters.
Re:How not to behave on GitHub issues by divs1210 on Tuesday June 13, 2017 @12:40PM (#14546127)
Yes, but the package on npm is, indeed, corrupt and the latest semantic version.

Anyone creating a fresh project right now with uglifyjs somewhere down the build chain will face this issue.

The only way to resolve this is by publishing a fresh, correct version to npm ragardless of what caused the issue.

The authors have failed to do this till now and the issue remains closed.

There are no comments on this comment yet.