The npm blog has been discontinued.
As foretold by the prophesies, another weekly npm v7 beta is now available.
tl;dr - run
npm i -g npm@next-7 right now, and tell us about any problems you encounter with it.
This fixes the
npm view --json output, adds test coverage, and switches us from
leven for the “Did you mean…?” message.
It does not yet fix some of the other issues that early beta testers have helpfully reported to us:
- A race condition during configuration loading can lead to a “bad marker” error being thrown if there is a file at
/usr/local/lib/node_modules/npm/npmrc. (Which npm v6 puts there when it installs npm v7.)
- Unresolvable peer dependency conflicts are not reported very usefully.
package.jsonsets indentation style to two-spaces when saving dependencies.
- Fresh installs with old lockfiles can lead to missing executables and (if the lockfile is old enough!) even missing dependencies.
We expect these issues to be fixed in upcoming beta updates soon.
As always, please report any problems you encounter! We are grateful for your help in npm’s ongoing improvement.
b718b0e28#1657 display multiple versions when using
9e7cc42f6#1071 migrate from
85027f40c#1664 refactor and add tests for
6e03e5583#1672 refactor and add tests for
Replace some environment variables that were excluded. This implements the amendment to RFC0021.
Bring back support for
npm audit --production, fix a minor
npm version annoyance, and track down a very serious issue where a project could be blown away when it matches a meta-dep in the tree.
@email@example.comAdd support for
npm audit --production
New notification style for updates, and a working doctor.
cf2819210#1622 Improve abbrevs for install and help
d062b2c02new npm-specific update-notifier implementation
f6d468a3bupdate doctor command
b8b4d77af#1638 Direct users to our GitHub issues instead of npm.community
Fix some issues found in the beta pubish process, and initial attempts to use npm v7 with citgm.