Release: npm@6.6.0-next.1


(Audrey Eschright) #1

A new pre-release of the npm cli has been tagged! You can install it with npm i -g npm@next or try it out with npx npm@next …

Prereleases are promoted to latest after about a week if no serious issues stop them. Try it out, tell us what you think! :dancer:

latest: 6.5.0
next: 6.6.0-next.1


Today is an auspicious day! This release marks the end of a massive internal refactor to npm that means we finally got rid of the legacy npm-registry-client in favor of the shiny, new, window.fetch -like npm-registry-fetch .

Now, the installer had already done most of this work with the release of npm@5 , but it turns out every other command still used the legacy client. This release updates all of those commands to use the new client, and while we’re at it, adds a few extra goodies:

  • All OTP-requiring commands will now prompt . --otp is no longer required for dist-tag , access , et al.
  • We’re starting to integrate a new config system which will eventually get extracted into a standalone package.
  • We now use libnpm for the API functionality of a lot of our commands! That means you can install a library if you want to write your own tooling around them.
  • There’s now an npm org command for managing users in your org.
  • pacote now consumes npm-style configurations, instead of its own naming for various config vars. This will make it easier to load npm configs using libnpm.config and hand them directly to pacote .

There’s too many commits to list all of them here, so check out the PR if you’re curious about details: