News for hackers. Stuff that matters.
Re:How not to behave on GitHub issues by mdlap on Tuesday June 13, 2017 @06:59AM (#14543944)
Inappropriate: Users being impolite and overly demanding. Inappropriate: Maintainers (and supporters) insisting that a problem in their publishing process (whether or not they caused it) isn't their problem because the code works.

Both sides had legitimate grievances, and both sides did a poor job of trying to resolve them.

Re:How not to behave on GitHub issues by tinus_hn on Tuesday June 13, 2017 @08:12AM (#14544184)
You make a stupid mistake and people politely ask you to fix it. If you dismiss the polite people it's only a matter of time before you run into someone who is not polite.

It also doesn't help if your attitude is that if you think everyone else is being an idiot you don't stop and check if maybe the problem is with yourself.

Re:How not to behave on GitHub issues by boyakasha on Tuesday June 13, 2017 @08:27AM (#14544244)
What stupid mistake? It was an NPM bug.
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.