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 bui

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.