This website uses cookies on its adverts and sponsored links. By clicking the "Accept" button you are consenting to their use.

Read more

Accept


Mobile Tech Tracker
≡ sections
Home

Tech Advice

Tech Thoughts

Apps

Tech News

About

Welcome to Mobile Tech Tracker. Our mission is to help technically-minded people to become better versions of themselves and to help ordinary people to use modern smart technologies to their own advantage. If you want to support us, please consider visiting the pages of our advertisers.


Only use Node.js if you know what you are doing

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:

https://goo.gl/wnkQDH


Published by

Posted on 26 Feb 2018




Tech News


.NET Core 3 will not run on .NET Framework

.NET Core 3 will not run on .NET Framework


.NET Core is set to replace .NET Framework

.NET Core is set to replace .NET Framework


If .NET Core is good enough for Bing, it's good enough

If .NET Core is good enough for Bing, it's good enough


Why does Google want to know my location

Why does Google want to know my location


Q#, an emerging language for quantum computing

Q#, an emerging language for quantum computing


Share this:

Facebook Google LinkedIn Twitter Become a Patron!


More from Tech News


.NET Core 3 will not run on .NET Framework [VIDEO]


.NET Core is set to replace .NET Framework [VIDEO]


If .NET Core is good enough for Bing, it's good enough [VIDEO]


Why does Google want to know my location [VIDEO]


Q#, an emerging language for quantum computing [VIDEO]


Edge browser gets improved WebAssembly support [VIDEO]


Kubernetes gets fully integrated with Visual Studio [VIDEO]


Microsoft deploys an underwater data centre [VIDEO]


Microsoft grants organisations an easy access to blockchain [VIDEO]


Saving your mobile apps from the danger of rooted devices [VIDEO]

Privacy Policy

© Mobile Tech Tracker. All rights reserved. Unauthorised copying of any of this website's content is prohibited under international law.

For any queries, comments or suggestions, please write to info@mobiletechtracker.co.uk.