npm@4.6.1 breaks build ⚠️

[greenkeeperio-bot]

🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

---

Hello lovely humans,

npm just published its new version 4.6.1.

State	Failing tests ⚠️
Dependency	npm
New version	4.6.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build kept failing.

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

v4.6.1 (2017-04-21)

A little release to tide you over while we hammer out the last bits for npm@5.

FEATURES

• d13c9b2f2 init-package-json@1.10.0: The name: prompt is now package name: to make this less ambiguous for new users.

  The default package name is now a valid package name. For example: If your package directory has mixed case, the default package name will be all lower case.

• f08c66323 #16213 Add --allow-same-version option to npm version so that you can use npm version to run your version lifecycles and tag your git repo without actually changing the version number in your package.json. (@lucastheisen)

• f5e8becd0 Timing has been added throughout the install implementation. You can see it by running a command with --loglevel=timing. You can also run commands with --timing which will write an npm-debug.log even on success and add an entry to _timing.json in your cache with the timing information from that run. (@iarna)

BUG FIXES

• 9c860f2ed #16021 Fix a crash in npm doctor when used with a registry that does not support the ping API endpoint. (@watilde)
• 65b9943e9 #16364 Shorten the ELIFECYCLE error message. The shorter error message should make it much easier to discern the actual cause of the error. (@j-f1)
• a87a4a835 npmlog@4.0.2: Fix flashing of the progress bar when your terminal is very narrow. (@iarna)
• 41c10974f write-file-atomic@1.3.2: Wait for fsync to complete before considering our file written to disk. This will improve certain sorts of Windows diagnostic problems.
• 2afa9240c #16336 Don't ham-it-up when expecting JSON. (@bdukes)

DOCUMENTATION FIXES

• 566f3eebe #16296 Use a single convention when referring to the <command> you're running. (@desfero)
• ccbb94934 #16267 Fix a missing space in the example package.json. (@famousgarkin)

DEPENDENCY UPDATES

• ebde4ea33 hosted-git-info@2.4.2
• c46ad71bb init-package-json@1.9.6
• d856d570d npm-registry-client@8.1.1
• 4a2e14436 readable-stream@2.2.9
• f0399138e normalize-package-data@2.3.8

---

The new version differs by 26 commits .

• 3fb3f72 4.6.1
• 9abd882 doc: changelog for 4.6.1
• afa7c03 write-file-atomic@1.3.3
• 4d833af init-package-json@1.10.1
• 28bde7f 4.6.0
• dc3753a update AUTHORS
• 771c668 doc: changelog for 4.6.0
• a87a4a8 npmlog@4.0.2
• 41c1097 write-file-atomic@1.3.2
• f039913 normalize-package-data@2.3.8
• d13c9b2 init-package-json@1.10.0
• 9c860f2 doctor: do not crash w/ registries that do not support ping
• f08c663 version: Add --allow-same-version option
• ccbb949 doc: fixed package.json docs brace space typo
• 566f3ee doc: preserve same name convention for command

There are 26 commits in total. See the full diff.