The npm community forum has been discontinued.
To discuss usage of npm, visit the GitHub Support Community.
A new version has been released!
You can install it with
npm i -g npm@latest or try it out with
$ npx npm@latest ... !
As per our process, the prerelease cycle for 6.4.1 is now over and
firstname.lastname@example.org is the latest and greatest in npm technology. The changelog for 6.4.1 is identical to
email@example.com, as no particular regressions were found.
4bd40f543#42 Prevent blowing up on malformed responses from the
npm auditendpoint, such as with third-party registries. (@framp)
NO_PROXYsupport by renaming npm-side config to
--noproxy. The environment variable should still work. (@SneakyFish5)
update-notifierchecks when a CI environment is detected. (@Sibiraj-S)
1bc5b8cea#47 Fix issue where
postpackscripts would break if
packwas used with
firstname.lastname@example.org: No real changes in npm-packlist, but npm-bundled included a circular dependency fix, as well as adding a proper LICENSE file. (@isaacs)
email@example.com: Fixes issue where
npm ciwasn’t running the
preparelifecycle script when installing git dependencies (@edahlseng)
JSONStream@1.3.4: Fixes memory leak problem when streaming large files (like legacy npm search). (@daern91)
firstname.lastname@example.org: Fixes issue for Windows user where multiple
PATHvariables were being added to the environment and breaking things in all sorts of fun and interesting ways. (@JimiC)
email@example.com: Adds support for two more CI services (@watson)
de956405d#41 Add documentation for
95031b90c#48 Update republish time and lightly reorganize republish info. (@neverett)
firstname.lastname@example.org date in changelog. (@charmander)
3fea3166e#55 Align command descriptions in help text. (@erik)