Hi everybody, I’m Fred, new member of the CLI team. A new prerelease of the npm cli has been tagged (and it’s my first one!).
You can install it with npm i -g npm@next or try it out with npx npm@next …
Prereleases are promoted to latest after a week if no serious issues stop them. Please give it a whirl and tell us what you think!
REFACTORING OUT npm-REGISTRY-CLIENT
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,
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.
--otpis no longer required for
access, et al.
- We’re starting to integrate a new config system which will eventually get extracted into a standalone package.
- We now use
libnpmfor 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 orgcommand for managing users in your org.
pacotenow consumes npm-style configurations, instead of its own naming for various config vars. This will make it easier to load npm configs using
libnpm.configand hand them directly to
There’s too many commits to list all of them here, so check out the PR if you’re curious about details:
ae936f22c#2 Move rest of commands to
figgy-puddingfor configs. (@zkat)
npm dist-tagsthe same as
npm dist-tag ls. (@isaacs)
1065a7809#65 Add support for
IBM i. (@dmabupt)
890a74458npm.community#3278 Fix support for passing git binary path config with
90e55a143npm.community#2713 Check for
npm.config's existence in
error-handler.jsto prevent weird errors when failures happen before config object is loaded. (@BeniCheni)
a3ba0ccf1move rimraf to prod deps (@zkat)