If you choose a technology to deploy on your system, you need to at least know how to use it at the most fundamental level. However, recently, it became apparent that this did not apply to at least 4,000 Node.js developers, who have mixed up commands and ended up installing a sub-par pre-release version of NPM rather than it's latest production version.
NPM is the technology that makes Node.js so popular. It stands for "Node Package Manager" and allows Node.js developers to effortlessly download add-ons, tools and dependencies for their apps from a huge online repository. However, the latest pre-release version of NPM, 5.7.0, which was never marked as production-ready, had several significant issues with it.
Users who have downloaded pre-release package have experienced significant problems with their systems afterwards, which included servers crashing and permissions on the file systems being completely broken. Although some bugs on software that is not production-ready are expected, these are really serious defects and the software should not have ever made it to the pre-release stage with those. QA should have picked it up well before the release. However, those developers who have downloaded faulty software to their production servers are not without a blame either.
If you are a Node.js developer, it is absolutely crucial to know the difference between "latest" and "next" tags. "Latest" refers to the latest stable production-ready version, while "next" refers to a release candidate that is being prepared to become a production-ready, but is not yet recommended to be used in production. The NPM version that broke the servers was tagged as "next", not "latest". Sadly, 4,000 developers were not aware of this distinction.
For more information, follow this link:
Published by Mobile Tech Tracker
Posted on 26 Feb 2018