v6.8.0

This release includes an implementation of RFC #10, documenting an optional field that can be used to specify the directory path for a package within a monorepo.

NEW FEATURES

• 3663cdef2 #140 Update package.json docs to include repository.directory details. (@greysteil)

BUGFIXES

• 550bf703a Add @types to ignore list to fix git clean -fd. (@zkat)
• cdb059293 #144 Fix common.npm callback arguments. (@larsgw)
• 25573e9b9 npm.community#4770 Show installed but unmet peer deps. (@larsgw)
• ce2c4bd1a #149 Use figgy-config to make sure extra opts are there. (@zkat)
• 3c22d1a35 npm.community#5101 Fix ls-collaborators access error for non-scoped case. (@zkat)
• d5137091d npm.community#754 Fix issue with sub-folder local references. (@iarna) (@jhecking)

DEPENDENCY BUMPS

• d72141080 npm-registry-couchapp@2.7.1 (@zkat)
• 671cad1b1 npm-registry-fetch@3.9.0: Make sure publishing with legacy username:password _auth works again. (@zkat)
• 95ca1aef4 pacote@9.4.1 (@aeschright)
• 322fef403 normalize-package-data@2.5.0 (@aeschright)
• 32d34c0da npm-packlist@1.3.0 (@aeschright)
• 338571cf0 read-package-tree@5.2.2 (@zkat)

MISC

• 89b23a5f7 #120 Use const in lib/fetch-package-metadata.md. (@watilde)
• 4970d553c #126 Replace ronn with marked-man in .npmignore. (@watilde)
• d9b6090dc #138 Reduce work to test if executable ends with a 'g'. (@elidoran) (@larsgw)

v6.8.0-next.2

This release includes an implementation of RFC #10, documenting an optional field that can be used to specify the directory path for a package within a monorepo.

NEW FEATURES

• 3663cdef2 #140 Update package.json docs to include repository.directory details. (@greysteil)

BUGFIXES

• 550bf703a Add @types to ignore list to fix git clean -fd. (@zkat)
• cdb059293 #144 Fix common.npm callback arguments. (@larsgw)
• 91314e77b npm.community#4794 Fix hoisting of packages with peerDeps. (@sokra)
• 25573e9b9 npm.community#4770 Show installed but unmet peer deps. (@larsgw)
• ce2c4bd1a #149 Use figgy-config to make sure extra opts are there. (@zkat)
• 3c22d1a35 npm.community#5101 Fix ls-collaborators access error for non-scoped case. (@zkat)
• d5137091d npm.community#754 Fix issue with sub-folder local references. (@iarna) (@jhecking)

DEPENDENCY BUMPS

• d72141080 npm-registry-couchapp@2.7.1 (@zkat)
• 671cad1b1 npm-registry-fetch@3.9.0: Make sure publishing with legacy username:password _auth works again. (@zkat)
• 95ca1aef4 pacote@9.4.1 (@aeschright)
• 322fef403 normalize-package-data@2.5.0 (@aeschright)
• 32d34c0da npm-packlist@1.3.0 (@aeschright)

MISC

• 89b23a5f7 #120 Use const in lib/fetch-package-metadata.md. (@watilde)
• 4970d553c #126 Replace ronn with marked-man in .npmignore. (@watilde)
• d9b6090dc #138 Reduce work to test if executable ends with a 'g'. (@elidoran) (@larsgw)

v6.8.0-next.1

This release includes an implementation of RFC #10, documenting an optional field that can be used to specify the directory path for a package within a monorepo.

NEW FEATURES

• 3663cdef2 #140 Update package.json docs to include repository.directory details. (@greysteil)

BUGFIXES

• 550bf703a Add @types to ignore list to fix git clean -fd. (@zkat)
• cdb059293 #144 Fix common.npm callback arguments. (@larsgw)
• 91314e77b npm.community#4794 Fix hoisting of packages with peerDeps. (@sokra)
• 25573e9b9 npm.community#4770 Show installed but unmet peer deps. (@larsgw)
• ce2c4bd1a #149 Use figgy-config to make sure extra opts are there. (@zkat)
• 3c22d1a35 npm.community#5101 Fix ls-collaborators access error for non-scoped case. (@zkat)

DEPENDENCY BUMPS

• d72141080 npm-registry-couchapp@2.7.1 (@zkat)
• 671cad1b1 npm-registry-fetch@3.9.0: Make sure publishing with legacy username:password _auth works again. (@zkat)
• 95ca1aef4 pacote@9.4.1 (@aeschright)
• 322fef403 normalize-package-data@2.5.0 (@aeschright)
• 32d34c0da npm-packlist@1.3.0 (@aeschright)

MISC

• 89b23a5f7 #120 Use const in lib/fetch-package-metadata.md. (@watilde)
• 4970d553c #126 Replace ronn with marked-man in .npmignore. (@watilde)
• d9b6090dc #138 Reduce work to test if executable ends with a 'g'. (@elidoran) (@larsgw)

v6.8.0-next.0

This release includes an implementation of RFC #10, documenting an optional field that can be used to specify the directory path for a package within a monorepo.

NEW FEATURES

• 3663cdef2 #140 Update package.json docs to include repository.directory details. (@greysteil)

BUGFIXES

• 550bf703a Add @types to ignore list to fix git clean -fd. (@zkat)
• cdb059293 #144 Fix common.npm callback arguments. (@larsgw)
• 91314e77b npm.community#4794 Fix hoisting of packages with peerDeps. (@sokra)
• 25573e9b9 npm.community#4770 Show installed but unmet peer deps. (@larsgw)
• ce2c4bd1a #149 Use figgy-config to make sure extra opts are there. (@zkat)

DEPENDENCY BUMPS

• d72141080 npm-registry-couchapp@2.7.1 (@zkat)
• 671cad1b1 npm-registry-fetch@3.9.0: Make sure publishing with legacy username:password _auth works again. (@zkat)
• 95ca1aef4 pacote@9.4.1 (@aeschright)

MISC

• 89b23a5f7 #120 Use const in lib/fetch-package-metadata.md. (@watilde)
• 4970d553c #126 Replace ronn with marked-man in .npmignore. (@watilde)
• d9b6090dc #138 Reduce work to test if executable ends with a 'g'. (@elidoran) (@larsgw)

v6.7.0

Hey y'all! This is a quick hotfix release that includes some important fixes to npm@6.6.0 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.

NEW FEATURES

• 50463f58b Improve usage errors to npm org commands and add optional filtering to npm org ls subcommand. (@zkat)

BUGFIXES

• 4027070b0 Fix default usage printout for npm org so you actually see how it's supposed to be used. (@zkat)
• cfea6ea5b fix default usage message for npm hook (@zkat)

DOCS

• e959e1421 Add manpage for npm org command. (@zkat)

DEPENDENCY BUMPS

• 8543fc357 pacote@9.4.0: 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)
• 75475043b npm.community#4752 libnpmpublish@1.1.1: Fixes auth error for username/password legacy authentication. (@sreeramjayan)
• 0af8c00ac npm.community#4746 libcipm@3.0.3: Fixes issue with "cannot run in wd" errors for run-scripts. (@zkat)
• 5a7962e46 write-file-atomic@2.4.2: Fixes issues with leaking signal-exit instances and file descriptors. (@iarna)

v6.6.0

REFACTORING OUT npm-REGISTRY-CLIENT

Today is an auspicious day! This release marks the end of a massive internal refactor to npm that means we finally got rid of the legacy npm-registry-client in favor of the shiny, new, window.fetch-like npm-registry-fetch.

Now, the installer had already done most of this work with the release of npm@5, but it turns out every other command still used the legacy client. This release updates all of those commands to use the new client, and while we're at it, adds a few extra goodies:

• All OTP-requiring commands will now prompt. --otp is no longer required for dist-tag, access, et al.
• We're starting to integrate a new config system which will eventually get extracted into a standalone package.
• We now use libnpm for the API functionality of a lot of our commands! That means you can install a library if you want to write your own tooling around them.
• There's now an npm org command for managing users in your org.
• pacote now consumes npm-style configurations, instead of its own naming for various config vars. This will make it easier to load npm configs using libnpm.config and hand them directly to pacote.

There's too many commits to list all of them here, so check out the PR if you're curious about details:

• c5af34c05 npm-registry-client@REMOVED (@zkat)
• 4cca9cb90 ad67461dc 77625f9e2 6e922aefb 584613ea8 64de4ebf0 6cd87d1a9 2786834c0 514558e09 dec07ebe3 084741913 45aff0e02 846ddcc44 8971ba1b9 99156e081 ab2155306 b37a66542 d2af0777a e0b4c6880 ff72350b4 6ed943303 90a069e7d b24ed5fdc ec9fcc14f 8a56fa39e 41d19e18f 125ff9551 1c3b226ff 3c0a7b06b 08fcb3f0f c8135d97a ae936f22c #2

NEW FEATURES

• 02c837e01 #106 Make npm dist-tags the same as npm dist-tag ls. (@isaacs)
• 1065a7809 #65 Add support for IBM i. (@dmabupt)
• a22e6f5fc #131 Update profile to support new npm-profile API. (@zkat)

BUGFIXES

• 890a74458 npm.community#3278 Fix support for passing git binary path config with --git. (@larsgw)
• 90e55a143 npm.community#2713 Check for npm.config's existence in error-handler.js to prevent weird errors when failures happen before config object is loaded. (@BeniCheni)
• 134207174 npm.community#2569 Fix checking for optional dependencies. (@larsgw)
• 7a2f6b05d npm.community#4172 Remove tink experiments. (@larsgw)
• c5b6056b6 #123 Handle git branch references correctly. (@johanneswuerbach)
• f58b43ef2 npm.community#3983 Report any errors above 400 as potentially not supporting audit. (@zkat)
• a5c9e6f35 #124 Set default homepage to an empty string. (@anchnk)
• 5d076351d npm.community#4054 Fix npm-prefix description. (@larsgw)

DOCS

• 31a7274b7 #71 Fix typo in npm-token documentation. (@GeorgeTaveras1231)
• 2401b7592 Correct docs for fake-registry interface. (@iarna)

DEPENDENCIES

• 9cefcdc1d npm-registry-fetch@3.8.0 (@zkat)
• 1c769c9b3 pacote@9.1.0 (@zkat)
• f3bc5539b figgy-pudding@3.5.1 (@zkat)
• bf7199d3c npm-profile@4.0.1 (@zkat)
• 118c50496 semver@5.5.1 (@isaacs)
• eab4df925 libcipm@3.0.2 (@zkat)
• b86e51573 libnpm@1.4.0 (@zkat)
• 56fffbff2 get-stream@4.1.0 (@zkat)
• df972e948 npm-profile@REMOVED
  (@zkat)
• 32c73bf0e libnpm@2.0.1 (@zkat)
• 569491b80 licensee@5.0.0 (@zkat)
• a3ba0ccf1 move rimraf to prod deps
  (@zkat)
• f63a0d6cf spdx-license-ids@3.0.3 (@zkat)
• f350e714f aproba@2.0.0 (@aeschright)
• a67e4d8b2 byte-size@5.0.1 (@aeschright)
• [8bea4efa3](8...

v6.6.0-next.1

REFACTORING OUT npm-REGISTRY-CLIENT

Today is an auspicious day! This release marks the end of a massive internal refactor to npm that means we finally got rid of the legacy npm-registry-client in favor of the shiny, new, window.fetch-like npm-registry-fetch.

Now, the installer had already done most of this work with the release of npm@5, but it turns out every other command still used the legacy client. This release updates all of those commands to use the new client, and while we're at it, adds a few extra goodies:

• All OTP-requiring commands will now prompt. --otp is no longer required for dist-tag, access, et al.
• We're starting to integrate a new config system which will eventually get extracted into a standalone package.
• We now use libnpm for the API functionality of a lot of our commands! That means you can install a library if you want to write your own tooling around them.
• There's now an npm org command for managing users in your org.
• pacote now consumes npm-style configurations, instead of its own naming for various config vars. This will make it easier to load npm configs using libnpm.config and hand them directly to pacote.

There's too many commits to list all of them here, so check out the PR if you're curious about details:

• c5af34c05 npm-registry-client@REMOVED (@zkat)
• 4cca9cb90 ad67461dc 77625f9e2 6e922aefb 584613ea8 64de4ebf0 6cd87d1a9 2786834c0 514558e09 dec07ebe3 084741913 45aff0e02 846ddcc44 8971ba1b9 99156e081 ab2155306 b37a66542 d2af0777a e0b4c6880 ff72350b4 6ed943303 90a069e7d b24ed5fdc ec9fcc14f 8a56fa39e 41d19e18f 125ff9551 1c3b226ff 3c0a7b06b 08fcb3f0f c8135d97a ae936f22c #2

NEW FEATURES

• 02c837e01 #106 Make npm dist-tags the same as npm dist-tag ls. (@isaacs)
• 1065a7809 #65 Add support for IBM i. (@dmabupt)
• a22e6f5fc #131 Update profile to support new npm-profile API. (@zkat)

BUGFIXES

• 890a74458 npm.community#3278 Fix support for passing git binary path config with --git. (@larsgw)
• 90e55a143 npm.community#2713 Check for npm.config's existence in error-handler.js to prevent weird errors when failures happen before config object is loaded. (@BeniCheni)
• 134207174 npm.community#2569 Fix checking for optional dependencies. (@larsgw)
• 7a2f6b05d npm.community#4172 Remove tink experiments. (@larsgw)
• c5b6056b6 #123 Handle git branch references correctly. (@johanneswuerbach)
• f58b43ef2 npm.community#3983 Report any errors above 400 as potentially not supporting audit. (@zkat)
• a5c9e6f35 #124 Set default homepage to an empty string. (@anchnk)
• 5d076351d npm.community#4054 Fix npm-prefix description. (@larsgw)

DOCS

• 31a7274b7 #71 Fix typo in npm-token documentation. (@GeorgeTaveras1231)
• 2401b7592 Correct docs for fake-registry interface. (@iarna)

DEPENDENCIES

• 9cefcdc1d npm-registry-fetch@3.8.0 (@zkat)
• 1c769c9b3 pacote@9.1.0 (@zkat)
• f3bc5539b figgy-pudding@3.5.1 (@zkat)
• bf7199d3c npm-profile@4.0.1 (@zkat)
• 118c50496 semver@5.5.1 (@isaacs)
• eab4df925 libcipm@3.0.2 (@zkat)
• b86e51573 libnpm@1.4.0 (@zkat)
• 56fffbff2 get-stream@4.1.0 (@zkat)
• df972e948 npm-profile@REMOVED
  (@zkat)
• 32c73bf0e libnpm@2.0.1 (@zkat)
• 569491b80 licensee@5.0.0 (@zkat)
• a3ba0ccf1 move rimraf to prod deps
  (@zkat)
• f63a0d6cf spdx-license-ids@3.0.3 (@zkat)
• f350e714f aproba@2.0.0 (@aeschright)
• a67e4d8b2 byte-size@5.0.1 (@aeschright)
• [8bea4efa3](8...

v6.6.0-next.0

REFACTORING OUT npm-REGISTRY-CLIENT

Today is an auspicious day! This release marks the end of a massive internal refactor to npm that means we finally got rid of the legacy npm-registry-client in favor of the shiny, new, window.fetch-like npm-registry-fetch.

Now, the installer had already done most of this work with the release of npm@5, but it turns out every other command still used the legacy client. This release updates all of those commands to use the new client, and while we're at it, adds a few extra goodies:

• All OTP-requiring commands will now prompt. --otp is no longer required for dist-tag, access, et al.
• We're starting to integrate a new config system which will eventually get extracted into a standalone package.
• We now use libnpm for the API functionality of a lot of our commands! That means you can install a library if you want to write your own tooling around them.
• There's now an npm org command for managing users in your org.
• pacote now consumes npm-style configurations, instead of its own naming for various config vars. This will make it easier to load npm configs using libnpm.config and hand them directly to pacote.

There's too many commits to list all of them here, so check out the PR if you're curious about details:

• c5af34c05 npm-registry-client@REMOVED (@zkat)
• 4cca9cb90 ad67461dc 77625f9e2 6e922aefb 584613ea8 64de4ebf0 6cd87d1a9 2786834c0 514558e09 dec07ebe3 084741913 45aff0e02 846ddcc44 8971ba1b9 99156e081 ab2155306 b37a66542 d2af0777a e0b4c6880 ff72350b4 6ed943303 90a069e7d b24ed5fdc ec9fcc14f 8a56fa39e 41d19e18f 125ff9551 1c3b226ff 3c0a7b06b 08fcb3f0f c8135d97a ae936f22c #2 Move rest of commands to npm-registry-fetch and use figgy-pudding for configs. (@zkat)

NEW FEATURES

• 02c837e01 #106 Make npm dist-tags the same as npm dist-tag ls. (@isaacs)
• 1065a7809 #65 Add support for IBM i. (@dmabupt)

BUGFIXES

• 890a74458 npm.community#3278 Fix support for passing git binary path config with --git. (@larsgw)
• 90e55a143 npm.community#2713 Check for npm.config's existence in error-handler.js to prevent weird errors when failures happen before config object is loaded. (@BeniCheni)

DOCS

• 31a7274b7 #71 Fix typo in npm-token documentation. (@GeorgeTaveras1231)

DEPENDENCIES

• 9cefcdc1d npm-registry-fetch@3.8.0 (@zkat)
• 1c769c9b3 pacote@9.1.0 (@zkat)
• f3bc5539b figgy-pudding@3.5.1 (@zkat)
• bf7199d3c npm-profile@4.0.1 (@zkat)
• 118c50496 semver@5.5.1 (@isaacs)
• eab4df925 libcipm@3.0.2 (@zkat)
• b86e51573 libnpm@1.4.0 (@zkat)
• 56fffbff2 get-stream@4.1.0 (@zkat)
• df972e948 npm-profile@REMOVED (@zkat)
• 32c73bf0e libnpm@2.0.1 (@zkat)
• 569491b80 licensee@5.0.0 (@zkat)
• a3ba0ccf1 move rimraf to prod deps (@zkat)

v6.5.0

NEW FEATURES

• fc1a8d185 Backronym npm ci to npm clean-install. (@zkat)
• 4be51a9cc #81 Adds 'Homepage' to outdated --long output. (@jbottigliero)

BUGFIXES

• 89652cb9b npm.community#1661 Fix sign-git-commit options. They were previously totally wrong. (@zkat)
• 414f2d1a1 npm.community#1742 Set lowercase headers for npm audit requests. (@maartenba)
• a34246baf #75 Fix npm edit handling of scoped packages.
  (@larsgw)* d3e8a7c72 npm.community#2303 Make summary output for npm ci go to stdout, not stderr. (@alopezsanchez)
• 71d8fb4a9 npm.community#1377 Close the file descriptor during publish if exiting upload via an error. This will prevent strange error messages when the upload fails and make sure
  cleanup happens correctly. (@macdja38)

DOCS UPDATES

• b1a8729c8 #60 Mention --otp flag when prompting for OTP. (@bakkot)
• bcae4ea81 #64 Clarify that git dependencies use the default branch, not just master. (@zckrs)
• 15da82690 #72 bash_completion.d dir is sometimes found in /etc not /usr/local. (@RobertKielty)
• 8a6ecc793 #74 Update OTP documentation for dist-tag add to clarify --otp is needed right now. (@scotttrinh)
• dcc03ec85 #82 Note that prepare runs when installing git dependencies. (@seishun)
• a91a470b7 #83 Specify that --dry-run isn't available in older versions of npm publish. (@kjin)
• 1b2fabcce #96 Fix inline code tag issue in docs. (@midare)
• 6cc70cc19 #68 Add semver link and a note on empty string format to deprecate doc. (@neverett)
• 61dbbb7c3 Fix semver docs after version update. (@zkat)
• 4acd45a3d #78 Correct spelling across various docs. (@hugovk)

DEPENDENCIES

• 4f761283e figgy-pudding@3.5.1 (@zkat)
• 3706db0bc npm.community#1764 ssri@6.0.1 (@zkat)
• 83c2b117d bluebird@3.5.2 (@petkaantonov)
• 2702f46bd ci-info@1.5.1 (@watson)
• 4db6c3898 config-chain@1.1.1:2 (@dawsbot)
• 70bee4f69 glob@7.1.3 (@isaacs)
• e469fd6be
opener@1.5.1: Fix browser opening under Windows Subsystem for Linux (WSL). (@thijsputman)
• 03840dced
semver@5.5.1 (@iarna)
• 161dc0b41 bluebird@3.5.3 (@petkaantonov)
• bb6f94395 graceful-fs@4.1.1:5 (@isaacs)
• 43b1f4c91 tar@4.4.8 (@isaacs)
• ab62afcc4 npm-packlist@1.1.1:2 (@isaacs)
• 027f06be3 ci-info@1.6.0 (@watson)

MISCELLANEOUS

• 27217dae8 #70 Automatically audit dependency licenses for npm itself. (@kemitchell)

v6.5.0-next.0

This release became npm@6.5.0.