rally25rs commented an hour ago
I almost hate to contribute to this, but a hopefully informative bit of information:
This issue is made worse by the version tagging
latest: 5.6.0
next: 5.7.0
because npm upgrade does not take that into account and will pull the newest version (5.7.0).
Because of this, you should not npm upgrade -g npm or else you will get these pre-release builds. npm itself will tell you to run npm install -g npm isntead, which does pull latest and ignore that next is newer:
~ 🐒 npm -v
5.5.1
╭─────────────────────────────────────╮
│ │
│ Update available 5.5.1 → 5.6.0 │
│ Run npm i -g npm to update │
│ │
╰─────────────────────────────────────╯
~ 🐒 npm i -g npm
+ npm@5.6.0
added 27 packages, removed 11 packages and updated 38 packages in 7.544s
~ 🐒 npm -v
5.6.0
~ 🐒 npm upgrade -g npm
+ npm@5.7.0
added 63 packages, removed 6 packages and updated 49 packages in 8.432s```
~ 🐒 npm -v
5.7.0
so you can protect yourself from inadvertently getting these pre-release builds into our production environments by sticking to npm i -g.