[email protected] untested ⚠️

[greenkeeperio-bot]

Hello lovely humans,

npm just published its new version 4.5.0.

State	No tests ⚠️
Dependency	npm
New version	4.5.0
Type	devDependency

This version is covered by your current version range, but I could not detect automated tests for this project. Without a test suite I can not really tell whether your project still works.

I was looking at the latest commit of your default branch, but GitHub said there is no status attached to it.

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.5.0 (2017-03-24)

Welcome a wrinkle on npm's registry API!

Codename: Corgi

This release has some bug fixes, but it's mostly about bringing support for MUCH smaller package metadata. How much smaller? Well, for npm itself it reduces 416K of gzip compressed JSON to 24K.

As a user, all you have to do is update to get to use the new API. If you're interested in the details we've documented the changes in detail.

CORGUMENTS

Package metadata: now smaller. This means a smaller cache and less to download.

• 86dad0d74 Add support for filtered package metadata. (@iarna)
• 41789cffa [email protected] (@iarna)

NO SHRINKWRAP, NO PROBLEM

Previously we needed to extract every package's tarball to look for an npm-shrinkwrap.json before we could begin working through what its dependencies were. This was one of the things stopping npm's network accesses from happening more concurrently. The new filtered package metadata provides a new key, _hasShrinkwrap. When that's set to false then we know we don't have to look for one.

• 4f5060eb3 #15969 Add support for skipping npm-shrinkwrap.json extraction when the registry can affirm that one doesn't exist. (@iarna)

INTERRUPTING SCRIPTS

• 878aceb25 #16129 Better handle Ctrl-C while running scripts. npm will now no longer exit until the script it is running has exited. If you press Ctrl-C a second time it kill the script rather than just forwarding the Ctrl-C. (@jaridmargolin)

DEPENDENCY UPDATES:

• def75eebf [email protected]: Preserve case of the user name part of shortcut specifiers, previously they were lowercased. (@iarna)
• eb3789fd1 [email protected]: Add support for VS2017 and Chakracore improvements. (@refack) (@kunalspathak)
• 245e25315 [email protected] (@mcollina)
• 30357ebc5 [email protected] (@isaacs)

---

The new version differs by 104 commits .

• 5d17fc9 4.5.0
• 3f88cb8 update AUTHORS
• cac64b7 doc: Fix release dates in changelog
• c97980b doc: update Changelog for 4.5.0
• bd624bf npm: Replace http: URL in npm-shrinkwrap with https:
• 878aceb lifecycle: On SIGINT, ensure process stays alive until child exits
• 86dad0d extract: support minified packuments
• 95d4fc8 fetch-package-metadata: Support the _hasShrinkwrap registry metadata
• 6400d3a script: fix lint error
• 30357eb [email protected]
• 245e253 [email protected]
• eb3789f [email protected]
• def75ee [email protected]
• 41789cf [email protected]
• 63468a6 4.4.4

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

---

✨ Try the all new Greenkeeper GitHub Integration ✨
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. Screencast Try it today. Free for private repositories during beta.