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 ... !
This is a quick hotfix release that includes some important fixes to
firstname.lastname@example.org related to the large rewrite/refactor. We’re tagging it as a feature release because the changes involve some minor new features, and semver is semver, but there’s nothing major here.
50463f58bImprove usage errors to
npm orgcommands and add optional filtering to
npm org lssubcommand. (@zkat)
4027070b0Fix default usage printout for
npm orgso you actually see how it’s supposed to be used. (@zkat)
cfea6ea5bfix default usage message for npm hook (@zkat)
email@example.com: Fall back to “fullfat” packuments on ETARGET errors. This will make it so that, when a package is published but the corgi follower hasn’t caught up, users can still install a freshly-published package. (@zkat)
firstname.lastname@example.org: Fixes auth error for username/password legacy authentication. (@sreeramjayan)
email@example.com: Fixes issue with “cannot run in wd” errors for run-scripts. (@zkat)
firstname.lastname@example.org: Fixes issues with leaking
signal-exitinstances and file descriptors. (@iarna)