Hello 👋

🚀🚀🚀

npm just published its new version 3.9.0, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of npm – otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴

GitHub Release

v3.9.0 (2016-05-05)

Wow! This is a big release week! We've completed the fixes that let the test suite pass on Windows, plus more general bug fixes we found while fixing things on Windows. Plus a warning to help folks work around a common footgun. PLUS an improvement to how npm works with long cache timeouts.

INFINITE CACHE A LITTLE BETTER

• 111ae3e #8581 When a package is fetched from the cache which cannot satisfy the version requirements, an attempt to fetch it from the network is made. This is helpful for folks using high values for --cache-min who are willing to accept possibly not-the-most-recent modules in return for less network traffic. (@Zirak)

WARNING: FOOTGUN

• 60b9a05 #12475 Options can only start with ASCII dashes. Ordinarily this isn't a problem but many web documentation tools "helpfully" convert -- into an emdash (–), or - into an endash (–). If you copy and paste from this documentation your commands won't work the way you expect. This adds a warning that tries to be a little more descriptive about why your command is failing. (@iarna)

WINDOWS CI

We have Windows CI setup now! We still have to tweak it a little bit around paths to the git binaries, but it's otherwise ready!

• bb5d6cb #11444 Add AppVeyor to CI matrix. (@othiym23)

COVERAGE DATA

Not only do our tests produce coverage reports after they run now, we also automatically update Coveralls with results from Travis CI runs.

• 044cbab #11444 Enable coverage reporting for every test run. (@othiym23)

EVERYONE BUGS

• 37c6a51 #12150 Ensure that 'npm cache ls' outputs real filenames. Previously it would sometimes double up the package name in the path it printed. (@isaacs)
• d3ce0b2 #11444 Fix unbuilding bins for scoped modules. (@iarna)
• e928a30 #11444 Make handling of local modules (eg npm install /path/to/my/module) more consistent when saved to a package.json. There were bugs previously where it wouldn't consistently resolve relative paths in the same way. (@iarna)
• b820ed4 #11444 Under certain circumstances the paths produced for linking, either relative or absolute, would end up basing off the wrong virtual cwd. This resulted in failures for npm link in these situations. (@iarna)

WINDOWS BUGS

• 7380425 #11444 Scoped module names were not being correctly inferred from the path on Windows. (@zkat)
• 91fc24f #11444 Explore with a command to run didn't work properly in Windows– it would pop open a new cmd window and leave it there. (@iarna)

WINDOWS REFACTORING

• f07e643 #11444 Move exec path escaping out to its own function. This turns out to be tricky to get right because how you escape commands to run on Windows via cmd is different then how you escape them at other times. Specifically, you HAVE to quote each directory segment that has a quote in it, that is: C:\"Program Files"\MyApp\MyApp.exe By contrast, if that were an argument to a command being run, you CAN'T DO quote it that way, instead you have to wrap the entire path in quotes, like so: "C:\Program Files\MyApp\MyApp.exe". (@iarna)
• 2e01d29 #11444 Create a single function for detecting if we're running on Windows (and using a Windows shell like cmd) and use this instead of doing it one-off all over the place. (@iarna)

FIX WINDOWS TESTS

As I said before, our tests are passing on Windows! 🎉

• ef0dd74 #11444 The fruits of many weeks of labor, fix our tests to pass on Windows. (@zkat) (@iarna)

DEPENDENCY UPDATES

• 8fccda8 #11444 normalize-git-url@3.0.2: Fix file URLs on Windows. (@zkat)
• f53a154 readable-stream@2.1.2: When readable-stream is disabled, reuse result of require('stream') instead of calling it every time. (@calvinmetcalf)
• 02841cf #11444 realize-package-specifier@3.0.2: Resolve local package paths relative to package root, not cwd. (@zkat) (@iarna)
• 247c1c5 #11444 npm-package-arg@4.1.1: Fix Windows file URIs with leading slashes. (@zkat)
• 365c72b which@1.2.8 (@isaacs)
• e568caa graceful-fs@4.1.4 (@isaacs)
• 304b974 #11444 standard@6.0.8 (@feross)

The new version differs by 84 commits .

• 9e03561 3.9.0
• 562ad70 update AUTHORS
• 7e6fd66 doc: changelog for 3.9.0
• 365c72b which@1.2.8
• f53a154 readable-stream@2.1.2
• e568caa graceful-fs@4.1.4
• 111ae3e cache: Never trust the cache if we can't find a matching version
• 4d19fc5 test: don't pass coveralls token to registry child test
• ae9c0f3 test: ignore scripts in builtin-config
• 37c6a51 file-completion: Ensure that 'npm cache ls' outputs real filenames
• 60b9a05 npm: Warn if argument starts with non-ascii dash
• 304b974 standard@6.0.8
• e498dcb src: bring code up to standard@6 compatibility
• ef0dd74 test: fix Windows-specific test issues
• f07e643 common-tap: Factor out exec path escaping

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

This pull request was created by greenkeeper.io.
It keeps your software up to date, all the time.