3 ms·
From: https://github.com/npm/npm/releases/tag/v5.7.1 https://github.com/npm/npm/releases/tag/v5.7.1 "Thankfully, it only affected users running npm@next, which
by InclinedPlane 9y ago
From: https://github.com/npm/npm/releases/tag/v5.7.1 https://github.com/npm/npm/releases/tag/v5.7.1
"Thankfully, it only affected users running npm@next, which is part of our staggered release system, which we use to prevent issues like this from going out into the wider world before we can catch them. Users on latest would have never seen this!"
If you are updating to the latest pre-release of something within mere hours of it dropping and you are updating production systems (presumably that have some business value) with no previous testing then the consequences of that aren't on the devs they are 100% on you. And you don't deserve to call yourself an IT (or Ops or DevOps or what-have-you) professional, that is amateurish behavior in the extreme.