The npm blog has been discontinued.
Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog.
v6.0.0-next.1
NEW FEATURES
a9e722118
#20256 Add support for managing npm webhooks. This brings over functionality previously provided by thewombat
CLI. (@zkat)8a1a64203
#20126 Addnpm cit
command that’s equivalent ofnpm ci && npm t
that’s equivalent ofnpm it
. (@SimenB)fe867aaf1
49d18b4d8
ff6b31f77
78eab3cda
Therequires
field in your lock-file will be upgraded to use ranges from versions on your first use of npm. (@iarna)cf4d7b4de
#20257 Add shasum and integrity to the newnpm view
output. (@zkat)
BUG FIXES
685764308
Fix a bug where OTPs passed in via the commandline would have leading zeros deleted resulted in authentication failures. (@iarna)8f3faa323
6800f76ff
ec90c06c7
825b5d2c6
4785f13fb
bd16485f5
Restore the ability to bundle dependencies that are uninstallable from the registry. This also eliminates needless registry lookups for bundled dependencies.Fixed a bug where attempting to install a dependency that is bundled inside another module without reinstalling that module would result in ENOENT errors. (@iarna)
429498a8c
#20029 Allow packages with non-registry specifiers to follow the fast path that the we use with the lock-file for registry specifiers. This will improve install time especially when operating only on the package-lock (--package-lock-only
). (@zkat)Fix the a bug where
npm i --only=prod
could remove development dependencies from lock-file. (@iarna)834b46ff4
#20122 Improve the update-notifier messaging (borrowing ideas from pnpm) and eliminate false positives. (@zkat)f9de7ef3a
#20154 Let version succeed whenpackage-lock.json
is gitignored. (@nwoltman)f8ec52073
#20212 Ensure that we only create anetc
directory if we are actually going to write files to it. (@buddydvd)ab489b753
#20140 Note in documentation thatpackage-lock.json
version gets touched bynpm version
. (@srl295)857c2138d
#20032 Fix bug where unauthenticated errors would get reported as both 404s and 401s, i.e.npm ERR! 404 Registry returned 401
. In these cases the error message will now be much more informative. (@iarna)d2d290bca
#20082 Allow optional @ prefix on scope withnpm team
commands for parity with other commands. (@bcoe)b5babf0a9
#19580 Improve messaging when two-factor authentication is required while publishing. (@jdeniau)471ee1c5b
0da38b7b4
Fix a bug where optional status of a dependency was not being saved to the package-lock on the initial install. (@iarna)b3f98d8ba
9dea95e31
Ensure that--no-optional
does not remove optional dependencies from the lock-file. (@iarna)
MISCELLANEOUS
DEPENDENCY UPDATES
73dc97455
zkat/cipm#46libcipm@1.6.2
: Detect binding.gyp for default install lifecycle. Let’snpm ci
work on projects that have their own C code. (@caleblloyd)77c3f7a00
iferr@1.0.0
dce733e37
zkat/json-parse-better-errors#1json-parse-better-errors@1.0.2
(@Hoishin)c52765ff3
readable-stream@2.3.6
(@mcollina)e160adf9f
update-notifier@2.4.0
(@sindersorhus)9a9d7809e
marked@0.3.1
(@joshbruce)f2fbd8577
#20256figgy-pudding@2.0.1
(@zkat)44972d53d
#20256libnpmhook@3.0.0
(@zkat)cfe562c58
#20276node-gyp@3.6.2
3c0bbcb8e
zkat/npx#172libnpx@10.1.1
(@jdalton)0573d91e5
zkat/cacache#128cacache@11.0.1
(@zkat)396afa99f
figgy-pudding@3.1.0
(@zkat)e7f869c36
pacote@8.0.0
(@zkat)77dac72df
ssri@6.0.0
(@zkat)0b802f2a0
retry@0.12.0
(@iarna)4781b64bc
libnpmhook@4.0.1
(@zkat)7bdbaeea6
npm-package-arg@6.1.0
(@zkat)5f2bf4222
read-package-tree@5.2.1
(@zkat)