NPM v7: Next Version of Node.js package Manager is faster and leaner

Nearly two months after the Takeover by Github there are news for Version 7 of the Node.js package Manager.

What initially a small shock wave sent by the developer Community, it seems, at least not in a negative impact. This year, Github, NPM had taken over, the package management system, which had briefly celebrated before his ten-year-old birthday.

NPM v7 presented at Github Satellite for the first time

The Microsoft daughter was not only the promise that the product should remain free of charge. Rather, Github, wanted to contribute to that NPM is associated with greater vigour to the front. The already ongoing Work on Version 7 of the NPM approach the end.

On the virtual conference on Github Satellite on 6. In may 2020, NPM, had introduced a product Manager Edward Thompson NPM v7, and thus a wave of enthusiasm started. The main changes are rather subtle.

NPM v7 is leaner and faster

First, NPM is working much faster. The developers through a kind of Bootstrapping. They reduced the number of Outputs, and removed all the treatment methods for Node.js-versions that have been around for a long time. NPM v7 only supports Node.js 10 and up.

In addition, they took from the command-line Interface, all functions that could be more than the command line, such as the Tree Management. Also with NPM v7, all the manual Intervention is necessary to Package Handling to be superfluous.

The new module Arborist is a Refactoring of dealing with Package Trees in NPM, which is about the use of Dependency Trees that were created with yarn and pnpm.

NPM move massive amounts of data

NPM operated according to his Ex-chief technician Ahmad Nassri meanwhile, on a monthly basis, around 125 billion Requests a transfer volume of gigantic six petabytes, so 6,000 terabytes or 125,000 Gigabyte. A total of 1.3 million packages are hosted. The meaning of the NPM, the Javascript Ecosystem is overestimated so hard to.

With the Github Acquisition of the yet fragile business model based on it should be ended, that a sufficient number of customers for private, not free-to-use packages, find. Github wants to take over the fee-based business under its own name and NPM as a purely free public package management system to continue to exist.

Matching: Instead of Grunt, Gulp and co.: How to use npm as a Build Tool

This could also interest you

Ready to see us in action:

More To Explore
Enable registration in settings - general
Have any project in mind?

Contact us: