7 ms·
http://blog.npmjs.org/post/171169301000/v571 http://blog.npmjs.org/post/171169301000/v571 Thankfully, it only affected users running `npm@next`, which is par
by master-litty 9y ago
http://blog.npmjs.org/post/171169301000/v571 http://blog.npmjs.org/post/171169301000/v571
Thankfully, it only affected users running `npm@next`, which is part of our staggered release system
#STOPUSINGPRERELEASEWITHSUDO
Really now?
#ANGRYORANGEWEBSITE #PEOPLEGOTMAD
:)
- homulilly 9y agoI guess they're just refusing to acknowledge that upgrading npm installed the "prerelease" version?
- enzanki_ars 9y agoThis is just absolutely unprofessional. All tags: #ANGRYORANGEWEBSITE #PEOPLEGOTMAD #STOPUSINGPRERELEASESWITHSUDO #CLIHOTFIX #WEGOTUBB #LITERALLYKILLEDGITHUB Author: FEBRUARY 22, 2018 (9:53 AM) @MAYBEKATZ https://web.archive.org/web/20180222201315/http://blog.npmjs.org/post/171169301000/v571 https://web.archive.org/web/20180222201315/http://blog.npmjs...