#npx

Fico me perguntando porque ele não perde a oportunidade de ser um babaca comigo, um escroto! Logo eu que faço tudo para agradar, cuido dele, me preocupo, incentivo a crescer... Fico pensando se eu fosse mais bonita, se ele mudaria de opinião, se ele passaria a me tratar com mais cuidado e carinho... Mas como ele mesmo diz: whatever! Se a minha alma não é suficiente, ele nunca terá meu corpo!

It's only been a couple of days but we've got some bug fixes we wanted to get out to you all. We also believe that npx is ready to be bundled with npm, which we're really excited about!

npx!!!

npx is a tool intended to help round out the experience of using packages from the npm registry — the same way npm makes it super easy to install and manage dependencies hosted on the registry, npx is meant to make it easy to use CLI tools and other executables hosted on the registry. It greatly simplifies a number of things that, until now, required a bit of ceremony to do with plain npm.

@zkat has a great introduction post to npx that I highly recommend you give a read

fb040bee0 #17685 Bundle npx with npm itself. (@zkat)

BUG FIXES

9fe905c39 #17652 Fix max callstack exceeded loops with trees with circular links. (@iarna)

c0a289b1b #17606 Make sure that when write package.json and package-lock.json we always use unix path separators. (@Standard8)

1658b79ca #17654 Make npm outdated show results for globals again. Previously it never thought they were out of date. (@iarna)

06c154fd6 #17678 Stop flattening modules that have peer dependencies. We're making this change to support scenarios where the module requiring a peer dependency is flattened but the peer dependency itself is not, due to conflicts. In those cases the module requiring the peer dep can't be flattened past the location its peer dep was placed in. This initial fix is naive, never flattening peer deps, and we can look into doing something more sophisticated later on. (@iarna)

88aafee8b #17677 There was an issue where updating a flattened dependency would sometimes unflatten it. This only happened when the dependency had dependencies that in turn required the original dependency. (@iarna)

b58ec8eab #17626 Integrators who were building their own copies of npm ran into issues because make install and https://npmjs.com/install.sh weren't aware that npm install creates links now when given a directory to work on. This does not impact folks installing npm with npm install -g npm. (@iarna)

DOC FIXES

10bef735e #17645 Fix some github issue links in the 5.1.0 changelog (@schmod)

85fa9dcb2 #17634 Fix typo in package-lock docs. (@sonicdoe)

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.

FEATURES

1e3a46944 #17616 Add --link filter option to npm ls. (@richardsimko)

33df0aaa [email protected] (@zkat):

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.

BUGFIXES

33df0aaa [email protected] (@zkat):

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 npx` works again.

`update-notifier` will no longer run for the npx bundled with npm.

`npx <cmd>` in a subdirectory of your project should be able to find your `node_modules/.bin` now. Oops

8e979bf80 Revert 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-vacuum getting confused while removing symlinked things. (@iarna)

f153b5b22 #17706 Use semver to compare node versions in npm doctor instead of plain >comparison. (@leo-shopify)

542f7561 #17742 Fix issue where npm version would sometimes not commit package-locks. (@markpeterfejes)

51a9e63d #17777 Fix bug exposed by other bugfixes where the wrong package would be removed. (@iarna)

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 npx works again.

update-notifier will no longer run for the npx bundled with npm.

npx <cmd> in a subdirectory of your project should be able to find your node_modules/.bin now. Oops

DOCUMENTATION

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!

fb42d55a9 #17728 Document semver git urls in package.json docs. (@sankethkatta)

f398c700f #17684 Tweak heading hierarchy in package.json docs. (@sonicdoe)