As mentioned before, we're continuing to do relatively rapid, smaller releases as we keep working on stomping out
npm@5 issues! We've made a lot of progress since 5.0 already, and this release is no exception.
--linkfilter option to
npm ls. (@richardsimko)
- 4 new languages - Czech, Italian, Turkish, and Chinese (Traditional)! This means npx is available in 14 different languages!
- New --node-arg option lets you pass CLI arguments directly to node when the target binary is found to be a Node.js script.
- npx should now work on (most) Windows installs. A couple of issues remain.
- Prevent auto-fallback from going into an infinite loop when npx disappears.
npx npx npx npx npx npx npx npxworks again.
update-notifierwill no longer run for the npx bundled with npm.
npx <cmd>in a subdirectory of your project should be able to find your
8e979bf80Revert change where npm stopped flattening modules that required peerDeps. This caused problems because folks were using peer deps to indicate that the target of the peer dep needed to be able to require the dependency and had been relying on the fact that peer deps didn't change the shape of the tree (as of npm@3). The fix that will actually work for people is for a peer dep to insist on never being installed deeper than the the thing it relies on. At the moment this is tricky because the thing the peer dep relies on may not yet have been added to the tree, so we don't know where it is. (@iarna)
7f28a77f3#17733 Split remove and unbuild actions into two to get uninstall lifecycles and the removal of transitive symlinks during uninstallation to run in the right order. (@iarna)
637f2548f#17748 When rolling back use symlink project-relative path, fixing some issues with
fs-vacuumgetting confused while removing symlinked things. (@iarna)
f153b5b22#17706 Use semver to compare node versions in npm doctor instead of plain
542f7561#17742 Fix issue where
npm versionwould sometimes not commit package-locks. (@markpeterfejes)
51a9e63d#17777 Fix bug exposed by other bugfixes where the wrong package would be removed. (@iarna)
Have we mentioned we really like documentation patches? Keep sending them in! Small patches are just fine, and they're a great way to get started contributing to npm!