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.0 is now over and
email@example.com is the latest and greatest in npm technology.
6e9f04b0bnpm/cli#8 Search for authentication token defined by environment variables by preventing the translation layer from env variable to npm option from breaking
84bfd23e7npm/cli#35 Stop filtering out non-IPv4 addresses from
local-addrs, making npm actually use IPv6 addresses when it must. (@valentin2105)
792c8c709npm/cli#31 configurable audit level for non-zero exit
npm auditcurrently exits with exit code 1 if any vulnerabilities are found of any level. Add a flag of
npm auditto allow it to pass if only vulnerabilities below a certain level are found. Example:
npm audit --audit-level=highwill exit with 0 if only low or moderate level vulns are detected. (@lennym)
A very special dependency update event! Since the release of
firstname.lastname@example.org, an awkward version conflict that was preventing
request from begin flattened was resolved. This means two things:
- We’ve cut down the npm tarball size by another 200kb, to 4.6MB
npm auditnow shows no vulnerabilities for npm itself!
email@example.com: REVERT REVERT, newer versions of this library are broken and print ansi codes even when disabled. (@iarna)
firstname.lastname@example.org: Fixes errors with empty or string-only license fields. (@Gudahtt)
npm publishfrom list of commands not affected by
e2b0f0921npm/cli#36 Tweak formatting in repository field examples. (@noahbenham)
process.envexamples to make accessing certain
npm run-scriptsenvironment variables more clear. (@mwarger)