Update npm to the latest version 🚀

[greenkeeper]

Version 6.0.0 of npm was just published.

Dependency	npm
Current Version	5.8.0
Type	dependency

The version 6.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of npm.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 121 commits.

• 7e679fd 6.0.0
• 73e50a7 test: prepublish-only: Use our own copy of npm
• 82dfa54 6.0.0-next.2
• 408a7ff update AUTHORS
• 1b021d0 doc: update changelog for npm@6.0.0
• 9c1eb94 inflate-shrinkwrap: For git changelings use version as resolved
• 2facb35 has-modern-meta: Correctly identify git changelings
• e4ed976 install/deps: Let git deps w/ lock only match package.json
• 552ff6d audit: Ensure we don't mutate the shrinkwrap
• f2386e1 test: standard common-tap
• 1d8ac24 test: JSON parse error message changed slightly
• cd36a21 audit: Avoid config-meta's literal-only test
• 09c7348 test: Default audit to off when testing
• 8e71334 audit: Add docs
• be393a2 audit: Temporarily suppress git metadata till there's an opt-in

There are 121 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[greenkeeper]

Version 6.0.1 just got published.

Update to this version instead 🚀

Release Notes

v6.0.1

CTRL-C OUT DURING PACKAGE EXTRACTION AS MUCH AS YOU WANT!

• b267bbbb9 npm/lockfile#29 lockfile@1.0.4: Switches to signal-exit to detect abnormal exits and remove locks. (@Redsandro)

SHRONKWRAPS AND LACKFILES

If a published modules had legacy npm-shrinkwrap.json we were saving ordinary registry dependencies (name@version) to your package-lock.json as https:// URLs instead of versions.

• 89102c0d9 When saving the lock-file compute how the dependency is being required instead of using _resolved in the package.json. This fixes the bug that was converting registry dependencies into https:// dependencies. (@iarna)
• 676f1239a When encountering a https:// URL in our lockfiles that point at our default registry, extract the version and use them as registry dependencies. This lets us heal package-lock.json files produced by 6.0.0 (@iarna)

AUDIT AUDIT EVERYWHERE

You can't use it quite yet, but we do have a few last moment patches to npm audit to make it even better when it is turned on!

• b2e4f48f5 Make sure we hide stream errors on background audit submissions. Previously some classes of error could end up being displayed (harmlessly) during installs. (@iarna)
• 1fe0c7fea Include session and scope in requests (as we do in other requests to the registry). (@iarna)
• d04656461 Exit with non-zero status when vulnerabilities are found. So you can have npm audit as a test or prepublish step! (@iarna)
• fcdbcbacc Verify lockfile integrity before running. You'd get an error either way, but this way it's faster and can give you more concrete instructions on how to fix it. (@iarna)
• 2ac8edd42 Refuse to run in global mode. Audits require a lockfile and globals don't have one. Yet. (@iarna)
• 3dcc240db Timeout audit requests eventually. (@iarna)

Looking forward

We're still a way from having node@11, so now's a good time to ensure we don't warn about being used with it.

• ed1aebf55 Allow node@11, when it comes. (@iarna)

DOCUMENTATION IMPROVEMENTS

• b7fca1084 #20407 Update the lock-file spec doc to mention that we now generate the from field for git-type dependencies. (@watilde)
• 7a6555e61 #20408 Describe what the colors in outdated mean. (@teameh)

DEPENDENCY UPDATES

• 5e56b3209 npm-audit-report@1.0.8 (@evilpacket)
• 58a0b31b4 lock-verify@2.0.2 (@iarna)
• e7a8c364f zkat/pacote#148 pacote@8.1.1 (@redonkulus)
• 46c0090a5 tar@4.4.2 (@isaacs)
• 8a16db3e3 update-notifier@2.5.0 (@alexccl)
• 696375903 safe-buffer@5.1.2 (@feross)
• c949eb26a query-string@6.1.0 (@sindresorhus)

Commits

The new version differs by 32 commits.

• 1365694 6.0.1
• 7163421 doc: update changelog for npm@6.0.1 final
• ed1aebf unsupported: Allow node@11, when it comes
• 3dcc240 audit: Timeout audit requests eventually
• 279ef3a 6.0.1-next.0
• 44cad2d update AUTHORS
• b08d903 travis: Add node v10
• 328531a mailmap: Update with real names
• 3a94056 lock-verify@2.0.2 (fix bundling)
• 5702175 audit: Only report audit as being unsupported on 404 and >= 500
• cb560d4 doc: update changelog for npm@6.0.1
• 7a6555e docs: describe what colors in outdated mean
• b7fca10 docs: add from field back into git dependencies
• be51b38 makefile: call cache clean with --force
• 2ac8edd audit: Refuse to run in global mode

There are 32 commits in total.

See the full diff

[greenkeeper]

Version 6.1.0 just got published.

Update to this version instead 🚀

Release Notes

v6.1.0

Look at that! A feature bump! npm@6 was super-exciting not just because it used a bigger number than ever before, but also because it included a super shiny new command: npm audit. Well, we've kept working on it since then and have some really nice improvements for it. You can expect more of them, and the occasional fix, in the next few releases as more users start playing with it and we get more feedback about what y'all would like to see from something like this.

I, for one, have started running it (and the new subcommand...) in all my projects, and it's one of those things that I don't know how I ever functioned -without- it! This will make a world of difference to so many people as far as making the npm ecosystem a higher-quality, safer commons for all of us.

This is also a good time to remind y'all that we have a new RFCs repository, along with a new process for them. This repo is open to anyone's RFCs, and has already received some great ideas about where we can take the CLI (and, to a certain extent, the registry). It's a great place to get feedback, and completely replaces feature requests in the main repo, so we won't be accepting feature requests there at all anymore. Check it out if you have something you'd like to suggest, or if you want to keep track of what the future might look like!

NEW FEATURE: npm audit fix

This is the biggie with this release! npm audit fix does exactly what it says on the tin. It takes all the actionable reports from your npm audit and runs the installs automatically for you, so you don't have to try to do all that mechanical work yourself!

Note that by default, npm audit fix will stick to semver-compatible changes, so you should be able to safely run it on most projects and carry on with your day without having to track down what breaking changes were included. If you want your (toplevel) dependencies to accept semver-major bumps as well, you can use npm audit fix --force and it'll toss those in, as well. Since it's running the npm installer under the hood, it also supports --production and --only=dev flags, as well as things like --dry-run, --json, and --package-lock-only, if you want more control over what it does.

Give it a whirl and tell us what you think! See npm help audit for full docs!

• 3800a660d Add npm audit fix subcommand to automatically fix detected vulnerabilities. (@zkat)

OTHER NEW audit FEATURES

• 1854b1c7f #20568 Add support for npm audit --json to print the report in JSON format. (@finnp)
• 85b86169d #20570 Include number of audited packages in npm install summary output. (@zkat)
• 957cbe275 npm-audit-report@1.2.1: Overhaul audit install and detail output format. The new format is terser and fits more closely into the visual style of the CLI, while still providing you with the important bits of information you need. They also include a bit more detail on the footer about what actions you can take! (@zkat)

NEW FEATURE: GIT DEPS AND npm init <pkg>!

Another exciting change that came with npm@6 was the new npm init command that allows for community-authored generators. That means you can, for example, do npm init react-app and it'll one-off download, install, and run create-react-app for you, without requiring or keeping around any global installs. That is, it basically just calls out to npx.

The first version of this command only really supported registry dependencies, but now, @jdalton went ahead and extended this feature so you can use hosted git dependencies, and their shorthands.

So go ahead and do npm init facebook/create-react-app and it'll grab the package from the github repo now! Or you can use it with a private github repository to maintain your organizational scaffolding tools or whatnot. ✨

• 483e01180 #20403 Add support for hosted git packages to npm init <name>. (@jdalton)

FIX WRITE AFTER END ERROR

First introduced in 5.8.0, this finally puts to bed errors where you would occasionally see Error: write after end at MiniPass.write.

• 171f3182f node-tar#180 npm.community#35 pacote@8.1.5: Fix write-after-end errors. (@zkat)

DETECT CHANGES IN GIT SPECIFIERS

• 0e1726c03 We can now determine if the commitid of a git dependency in the lockfile is derived from the specifier in the package.json and if it isn't we now trigger an update for it. (@iarna)

OTHER BUGFIXES

• 442d2484f 2f0c88351 631d30a34 When requesting the update of a direct dependency that was also a transitive dependency to a version incompatible with the transitive requirement and you had a lock-file but did not have a node_modules folder then npm would fail to provide a new copy of the transitive dependency, resulting in an invalid lock-file that could not self heal. (@iarna)
• be5dd0f49 #20715 Cleanup output of npm ci summary report. (@legodude17)
• 98ffe4adb Node.js now has a test that scans for things that look like conflict markers in source code. This was triggering false positives on a fixture in a test of npm's ability to heal lockfiles with conflicts in them. (@iarna)
• a41c0393c #20538 Make the new npm view work when the license field is an object instead of a string. (@zkat)
• eb7522073 #20582 Add support for environments (like Docker) where the expected binary for opening external URLs is not available. (@bcoe)
• 212266529 #20536 Fix a spurious colon in the new update notifier message and add support for the npm canary. (@zkat)
• 5ee1384d0 #20597 Infer a version range when a package.json has a dist-tag instead of a version range in one of its dependency specs. Previously, this would cause dependencies to be flagged as invalid. (@zkat)
• 4fa68ae41 #20585 Make sure scoped bundled deps are shown in the new publish preview, too. (@zkat)
• 1f3ee6b7e cacache@11.0.2: Stop dropping size from metadata on npm cache verify. (@jfmartinez)
• 91ef93691 #20513 Fix nested command aliases. (@mmermerkaya)
• 18b2b3cf7 npm-lifecycle@2.0.3: Make sure different versions of the Path env var on Windows all get node_modules/.bin prepended when running lifecycle scripts. (@laggingreflex)

DOCUMENTATION

• a91d87072 #20550 Update required node versions in README. (@legodude17)
• bf3cfa7b8 Pull in changelogs from the last npm@5 release. (@iarna)
• b2f14b14c #20629 Make tone in publishConfig docs more neutral. (@jeremyckahn)

DEPENDENCY BUMPS

• 5fca4eae8 byte-size@4.0.3 (@75lb)
• d9ef3fba7 lru-cache@4.1.3 (@isaacs)
• f1baf011a request@2.86.0 (@simonv)
• 005fa5420 require-inject@1.4.3 (@iarna)
• 1becdf09a tap@11.1.5 (@isaacs)
• 3f2e306b8 Using npm audit fix, replace some transitive dependencies with security issues with versions that don't have any. (@iarna)
• 1d07134e0 tar@4.4.1: Dropping to 4.4.1 from 4.4.2 due to npm/node-tar#183 (@zkat)

Commits

The new version differs by 39 commits.

• 4c65cd9 6.1.0
• b152d3e scripts: Make release script include tests
• f29b7a6 doc: Changelog for 6.1.0
• 631d30a deps: Use shrinkwrap root for relative pathing
• 2f0c883 inflate-shrinkwrap: Stop shortcircuiting tree walks with fake children
• 442d248 shrinkwrap: Stop special-casing fake children in shrinkwraps
• 3f2e306 deps: audit-fix our transitive deps
• be5dd0f ci: pause log before logging summary (#20715)
• 0e1726c deps: Now that from is in the lockfile, tighten git matching
• 171f318 pacote@8.1.5
• 1d07134 tar@4.4.1
• 98ffe4a test: Make sure the naive node conflict scanner is ok
• a8d89d9 doc: Fix changelog for 6.0.1
• 83a7051 6.1.0-next.0
• 91d6f5f update AUTHORS

There are 39 commits in total.

See the full diff