Fork me on GitHub
#javascript
<
2018-02-22
>
mikerod17:02:37

I can’t view that issue some reason, github error

fellshard18:02:14

Weird, I'm seeing it okay on my machine :TM:

mikerod18:02:13

I get the github unicorn still

mikerod18:02:19

times out it seems

fellshard18:02:42

tl;dr sudo npm --help (and any other npm commands) run chown recursively on many root directories, effectively bricking the OS in many cases. The change that caused it was announced via blog posts etc. and was not tagged as pre-release in semver as it should have been, so it was being picked up as a mainline minor release and blowing up people's production servers.

fellshard18:02:35

Furthermore, maintainers were pushing the blame back on users for not testing updated packages before pushing those updates to prod, despite it being a joint failure due to the maintainers' violation of semver practices. So in general, a failure of engineering, thorough testing, communication, protocol, and community. All in a day's work for JS 9_9

mikerod18:02:19

Hah, thanks for the explanation. Yes, sounds like a mess.