Bump npm from 2.12.1 to 2.15.12

[dependabot[bot]]

Bumps npm from 2.12.1 to 2.15.12.

Changelog

Sourced from npm's changelog.

v2.15.12 (2017-03-24):

This version brings the latest node-gyp to a soon to be released Node.js 4.x. The node-gyp update is paticularly important to Windows folks due to its addition of Visual Studio 2017 support.

• cdd60e733 [email protected]: Improvements to how Python is located. New --devdir flag. Support for VS2017. Chakracore support on ARM. Remove path-array dependency, reducing size significantly. (@​bnoordhuis) (@​mhart) (@​refack) (@​kunalspathak)

v2.15.11 (2016-09-08):

On we go with our monthly release cadence! This week is pretty much all dependency updates and some documentation changes, as can be expected by now.

Note that npm@4 will almost certainly be released next month! It's not final what we'll end up doing as far as LTS support goes, but the current thinking is that, considering how small and resource-constrained our team is, support for npm@2 will be reduced to essentially maintenance, so we can better focus on npm@3 as the new LTS version (which will go into node@6), and npm@4 as our next main development version.

DOCUMENTATION UPDATES

• 8f71038 #13892 Update LICENSE file to match license on master. (@​rvagg)
• e81b4f1 #12438 Remind folks to use #!/usr/bin/env node in their bin scripts to make files executable directly. (@​mxstbr)
• f89789f #13655 Document line comment syntax for .npmrc. (@​mdjasper)
• 5cd3abc #13493 Document that the user config file can itself be configured either through the $NPM_CONFIG_USERCONFIG environment variable, or --userconfig command line flag. (@​jasonkarns)

... (truncated)

Commits

• 6a9b3ec 2.15.12
• 5d5e28c doc: update changelog for 2.15.12
• cdd60e7 [email protected]
• 6f1648b 2.15.11
• 1e2d7d1 update AUTHORS
• de1e1e5 doc: update changelog for 2.15.11 lts
• 4258b76 [email protected]
• 706775f deps: deduped request
• dd71ca0 doc: clarify how config files are configured
• 8bef026 [email protected]
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.