Software update: npm 5.0.4

JavaScript developers are probably familiar with npm, a repository for sharing JavaScript code. This can be as a package or a module where the difference is this page is discussed. By using npm you can avoid having to reinvent the wheel for every piece of functionality, npm also helps keep track of the JavaScript code used. For more information, we refer you to this page. The development team behind npm recently released version 5.0.4 with the following announcement:

v5.0.4

Hey y’all. This is another minor patch release with a variety of little fixes we’ve been accumulating~

• Fix npm doctor when hitting registries without ping.
• Fix invalid format error when setting cache-related headers.
• Fix spurious EINTEGRITY issue.
• #17076 Use legacy from field to improve upgrade experience from legacy shrinkwraps and installs.
• #17007 Restore loose semver parsing to match older npm behavior when running into invalid semver ranges in dependencies.
• #17005 Emulate npm@4’s behavior of simply marking the peerDep as invalid, instead of crashing.
• #16937 Workaround for separate bug where requested was somehow null.
• Better logging output for git errors.
• More scp-url fixes: parsing only worked correctly when a committish was present.
• Standardize package permissions on tarball extraction, instead of using perms from the tarball. This matches previous npm behavior and fixes a number of incompatibilities in the wild.
• Limit shallow cloning to hosts which are known to support it.