8000 deps: upgrade npm to 4.2.0 · nodejs/node@2767e2d · GitHub
[go: up one dir, main page]
Skip to content

Commit 2767e2d

Browse files
zkatMylesBorins
zkat
authored and
MylesBorins
committed
deps: upgrade npm to 4.2.0
PR-URL: #11389 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
1 parent 4b1b6b8 commit 2767e2d

File tree

300 files changed

+2797
-12053
lines changed
  • npm-edit.1
  • npm-explore.1
  • npm-help-search.1
  • npm-help.1
  • npm-init.1
  • npm-install-test.1
  • npm-install.1
  • npm-link.1
  • npm-logout.1
  • npm-ls.1
  • npm-outdated.1
  • npm-owner.1
  • npm-pack.1
  • npm-ping.1
  • npm-prefix.1
  • npm-prune.1
  • npm-publish.1
  • npm-rebuild.1
  • npm-repo.1
  • npm-restart.1
  • npm-root.1
  • npm-run-script.1
  • npm-search.1
  • npm-shrinkwrap.1
  • npm-star.1
  • npm-stars.1
  • npm-start.1
  • npm-stop.1
  • npm-team.1
  • npm-test.1
  • npm-uninstall.1
  • npm-unpublish.1
  • npm-update.1
  • npm-version.1
  • npm-view.1
  • npm-whoami.1
  • npm.1
  • man5
  • man7
  • node_modules
  • package.json
  • test/tap

    • Some content is hidden

    Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

    300 files changed

    +2797
    -12053
    lines changed

    ‎deps/npm/.mailmap‎

    Lines changed: 1 addition & 1 deletion
    Original file line numberDiff line numberDiff line change
    @@ -21,7 +21,7 @@ Evan Lucas <evan@btc.com> <evan.lucas@hattiesburgclinic.com>
    2121
    Evan Lucas <evan@btc.com> <evanlucas@me.com>
    2222
    Faiq Raza <faiqrazarizvi@gmail.com>
    2323
    Forbes Lindesay <forbes@lindesay.co.uk>
    24-
    Forrest L Norvell <ogd@aoaioxxysz.net> <forrest@npmjs.com>
    24+
    Forrest L Norvell <ogd@aoaioxxysz.net> <forrest@npmjs.com> <othiym23@gmail.com>
    2525
    Gabriel Barros <descartavel1@gmail.com>
    2626
    Geoff Flarity <geoff.flarity@gmail.com> <gflarity@raptvm-x02.(none)>
    2727
    Gregers Gram Rygg <gregers.gram.rygg@finn.no>

    ‎deps/npm/AUTHORS‎

    Lines changed: 4 additions & 0 deletions
    Original file line numberDiff line numberDiff line change
    @@ -446,3 +446,7 @@ Ville Lahdenvuo <tuhoojabotti@gmail.com>
    446446
    Natalie Wolfe <nwolfe@newrelic.com>
    447447
    Andrew Schmadel <aschmadel@learningobjects.com>
    448448
    Jonah Moses <jonahkmoses@gmail.com>
    449+
    Daijirō Wachi <daijiro.wachi@gmail.com>
    450+
    Dmitry Litvinchenko <karaliti@gmail.com>
    451+
    chocolateboy <chocolate@cpan.org>
    452+
    Henry Zhu <hi@henryzoo.com>

    ‎deps/npm/CHANGELOG.md‎

    Lines changed: 114 additions & 0 deletions
    Original file line numberDiff line numberDiff line change
    @@ -1,3 +1,117 @@
    1+
    ### v4.2.0 (2017-01-26):
    2+
    3+
    Hi all! I'm Kat, and I'm currently sitting in a train traveling at ~300km/h
    4+
    through Spain. So clearly, this release should have *something* to do with
    5+
    speed. And it does! Heck, with this release, you could say we're really
    6+
    _blazing_, even. 🌲🔥😏
    7+
    8+
    #### IMPROVED CLI SEARCH~
    9+
    10+
    You might recall if you've been keeping up that one of the reasons for a
    11+
    semver-major bump to `npm@4` was an improved CLI search (read: no longer blowing
    12+
    up Node). The work done for that new search system, while still relying on a
    13+
    full metadata download and local search, was also meant to act as groundwork for
    14+
    then-ongoing work on a brand-new, smarter search system for npm. Shortly after
    15+
    `npm@4` came out, the bulk of the server-side work was done, and with this
    16+
    release, the npm CLI has integrated use of the new endpoint for high-quality,
    17+
    fast-turnaround searches.
    18+
    19+
    No, seriously, it's *fast*. And *relevant*:
    20+
    21+
    [![GOTTA GO FAST! This is a gif of the new npm search returning results in around a second for `npm search web framework`.](https://cloud.githubusercontent.com/assets/17535/21954136/f007e8be-d9fd-11e6-9231-f899c12790e0.gif)](https://github.com/npm/npm/pull/15481)
    22+
    23+
    Give it a shot! And remember to check out the new website version of the search,
    24+
    too, which uses the same backend as the CLI now. 🎉
    25+
    26+
    Incidentally, the backend is a public service, so you can write your own search
    27+
    tools, be they web-based, CLI, or GUI-based. You can read up on the [full
    28+
    documentation for the search
    29+
    endpoint](https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md#get-v1search),
    30+
    and let us know about the cool things you come up with!
    31+
    32+
    * [`ce3ca51`](https://github.com/npm/npm/commit/ce3ca51ca2d60e15e901c8bf6256338e53e1eca2)
    33+
    [#15481](https://github.com/npm/npm/pull/15481)
    34+
    Add an internal `gunzip-maybe` utility for optional gunzipping.
    35+
    ([@zkat](https://github.com/zkat))
    36+
    * [`e322932`](https://github.com/npm/npm/commit/e3229324d507fda10ea9e94fd4de8a4ae5025c75) [`a53055e`](https://github.com/npm/npm/commit/a53055e423f1fe168f05047aa0dfec6d963cb211) [`a1f4365`](https://github.com/npm/npm/commit/a1f436570730c6e4a173ca92d1967a87c29b7f2d) [`c56618c`](https://github.com/npm/npm/commit/c56618c62854ea61f6f716dffe7bcac80b5f4144)
    37+
    [#15481](https://github.com/npm/npm/pull/15481)
    38+
    Add support for using the new npm search endpoint for fast, quality search
    39+
    results. Includes a fallback to "classic" search.
    40+
    ([@zkat](https://github.com/zkat))
    41+
    42+
    #### WHERE DID THE DEBUG LOGS GO
    43+
    44+
    This is another pretty significant change: Usually, when the npm process
    45+
    crashed, you would get an `npm-debug.log` in your current working directory.
    46+
    This debug log would get cleared out as soon as you ran npm again. This was a
    47+
    bit annoying because 1) you would get a random file in your `git status` that
    48+
    you might accidentally commit, and 2) if you hit a hard-to-reproduce bug and
    49+
    instinctually tried again, you would no longer have access to the repro
    50+
    `npm-debug.log`.
    51+
    52+
    So now, any time a crash happens, we'll save your debug logs to your cache
    53+
    folder, under `_logs` (`~/.npm` on *nix, by default -- use `npm config get
    54+
    cache` to see what your current value is). The cache will now hold a
    55+
    (configurable) number of `npm-debug.log` files, which you can access in the
    56+
    future. Hopefully this will help clean stuff up and reduce frustration from
    57+
    missed repros! In the future, this will also be used by `npm report` to make it
    58+
    super easy to put up issues about crashes you run into with npm. 💃🕺🏿👯‍♂️
    59+
    60+
    * [`04fca22`](https://github.com/npm/npm/commit/04fca223a0f704b69340c5f81b26907238fad878)
    61+
    [#11439](https://github.com/npm/npm/pull/11439)
    62+
    Put debug logs in `$(npm get cache)/_logs` and store multiple log files.
    63+
    ([@KenanY](https://github.com/KenanY))
    64+
    ([@othiym23](https://github.com/othiym23))
    65+
    ([@isaacs](https://github.com/isaacs))
    66+
    ([@iarna](https://github.com/iarna))
    67+
    68+
    #### DOCS
    69+
    70+
    * [`ae8e71c`](https://github.com/npm/npm/commit/ae8e71c2b7d64d782af287a21e146d7cea6e5273)
    71+
    [#15402](https://github.com/npm/npm/pull/15402)
    72+
    Add missing backtick in one of the `npm doctor` messages.
    73+
    ([@watilde](https://github.com/watilde), [@charlotteis](https://github.com/charlotteis))
    74+
    * [`821fee6`](https://github.com/npm/npm/commit/821fee6d0b12a324e035c397ae73904db97d07d2)
    75+
    [#15480](https://github.com/npm/npm/pull/15480)
    76+
    Clarify that unscoped packages can depend on scoped packages and vice-versa.
    77+
    ([@chocolateboy](https://github.com/chocolateboy))
    78+
    * [`2ee45a8`](https://github.com/npm/npm/commit/2ee45a884137ae0706b7c741c671fef2cb3bac96)
    79+
    [#15515](https://github.com/npm/npm/pull/15515)
    80+
    Update minimum supported Node version number in the README to `node@>=4`.
    81+
    ([@watilde](https://github.com/watilde))
    82+
    * [`af06aa9`](https://github.com/npm/npm/commit/af06aa9a357578a8fd58c575f3dbe55bc65fc376)
    83+
    [#15520](https://github.com/npm/npm/pull/15520)
    84+
    Add section to `npm-scope` docs to explain that scope owners will own scoped
    85+
    packages with that scope. That is, user `@alice` is not allowed to publish to
    86+
    `@bob/my-package` unless explicitly made an owner by user (or org) `@bob`.
    87+
    ([@hzoo](https://github.com/hzoo))
    88+
    * [`bc892e6`](https://github.com/npm/npm/commit/bc892e6d07a4c6646480703641a4d71129c38b6d)
    89+
    [#15539](https://github.com/npm/npm/pull/15539)
    90+
    Replace `http` with `https` and fix typos in some docs.
    91+
    ([@watilde](https://github.com/watilde))
    92+
    * [`1dfe875`](https://github.com/npm/npm/commit/1dfe875b9ac61a0ab9f61a2eab02bacf6cce583c)
    93+
    [#15545](https://github.com/npm/npm/pull/15545)
    94+
    Update Node.js download link to point to the right place.
    95+
    ([@watilde](https://github.com/watilde))
    96+
    97+
    #### DEPENDENCIES
    98+
    99+
    * [`b824bfb`](https://github.com/npm/npm/commit/b824bfbeb2d89c92762e9170b026af98b5a3668a)
    100+
    `ansi-regex@2.1.1`
    101+
    * [`81ea3e8`](https://github.com/npm/npm/commit/81ea3e8e4ea34cd9c2b418512dcb508abcee1380)
    102+
    `mississippi@1.3.0`
    103+
    104+
    #### MISC
    105+
    106+
    * [`98df212`](https://github.com/npm/npm/commit/98df212a91fd6ff4a02b9cd247f4166f93d3977a)
    107+
    [#15492](https://github.com/npm/npm/pull/15492)
    108+
    Update the "master" node version used for AppVeyor to `node@7`.
    109+
    ([@watilde](https://github.com/watilde))
    110+
    * [`d75fc03`](https://github.com/npm/npm/commit/d75fc03eda5364f12ac266fa4f66e31c2e44e864)
    111+
    [#15413](https://github.com/npm/npm/pull/15413)
    112+
    `npm run-script` now exits with the child process' exit code on exit.
    113+
    ([@kapals](https://github.com/kapals))
    114+
    1115
    ### v4.1.2 (2017-01-12)
    2116

    3117
    We have a twee little release this week as we come back from the holidays.

    ‎deps/npm/README.md‎

    Lines changed: 3 additions & 3 deletions
    Original file line numberDiff line numberDiff line change
    @@ -9,9 +9,9 @@ Much more info available via `npm help` once it's installed.
    99

    1010
    ## IMPORTANT
    1111

    12-
    **You need node v0.10 or higher to run this program.**
    12+
    **You need node v4 or higher to run this program.**
    1313

    14-
    To install an old **and unsupported** version of npm that works on node 0.3
    14+
    To install an old **and unsupported** version of npm that works on node v0.12
    1515
    and prior, clone the git repo and dig through the old tags and branches.
    1616

    1717
    **npm is configured to use npm, Inc.'s public package registry at
    @@ -84,7 +84,7 @@ for testing, or running stuff without actually installing npm itself.)
    8484
    Many improvements for Windows users have been made in npm 3 - you will have a better
    8585
    experience if you run a recent version of npm. To upgrade, either use [Microsoft's
    8686
    upgrade tool](https://github.com/felixrieseberg/npm-windows-upgrade),
    87-
    [download a new version of Node](http://nodejs.org/download/),
    87+
    [download a new version of Node](https://nodejs.org/en/download/),
    8888
    or follow the Windows upgrade instructions in the
    8989
    [npm Troubleshooting Guide](https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows).
    9090

    ‎deps/npm/appveyor.yml‎

    Lines changed: 1 addition & 1 deletion
    Original file line numberDiff line numberDiff line change
    @@ -5,7 +5,7 @@ environment:
    55
    # previous LTS is next most important
    66
    - nodejs_version: "4"
    77
    # then master
    8-
    - nodejs_version: "5"
    8+
    - nodejs_version: "7"
    99
    COVERALLS_REPO_TOKEN:
    1010
    secure: XdC0aySefK0HLh1GNk6aKrzZPbCfPQLyA4mYtFGEp4DrTuZA/iuCUS0LDqFYO8JQ
    1111
    platform:

    ‎deps/npm/doc/files/package.json.md‎

    Lines changed: 3 additions & 3 deletions
    Original file line numberDiff line numberDiff line change
    @@ -119,18 +119,18 @@ array of license objects:
    119119
    // Not valid metadata
    120120
    { "license" :
    121121
    { "type" : "ISC"
    122-
    , "url" : "http://opensource.org/licenses/ISC"
    122+
    , "url" : "https://opensource.org/licenses/ISC"
    123123
    }
    124124
    }
    125125

    126126
    // Not valid metadata
    127127
    { "licenses" :
    128128
    [
    129129
    { "type": "MIT"
    130-
    , "url": "http://www.opensource.org/licenses/mit-license.php"
    130+
    , "url": "https://www.opensource.org/licenses/mit-license.php"
    131131
    }
    132132
    , { "type": "Apache-2.0"
    133-
    , "url": "http://opensource.org/licenses/apache2.0.php"
    10293
    133+
    , "url": "https://opensource.org/licenses/apache2.0.php"
    134134
    }
    135135
    ]
    136136
    }

    ‎deps/npm/doc/misc/npm-config.md‎

    Lines changed: 17 additions & 1 deletion
    Original file line numberDiff line numberDiff line change
    @@ -576,6 +576,13 @@ stderr.
    576576
    If the `color` config is set to true, then this stream will receive
    577577
    colored output if it is a TTY.
    578578

    579+
    ### logs-max
    580+
    581+
    * Default: 10
    582+
    * Type: Number
    583+
    584+
    The maximum number of log files to store.
    585+
    579586
    ### long
    580587

    581588
    * Default: false
    @@ -844,12 +851,21 @@ Space-separated options that limit the results from search.
    844851

    845852
    Space-separated options that are always passed to search.
    846853

    854+
    ### searchlimit
    855+
    856+
    * Default: 20
    857+
    * Type: Number
    858+
    859+
    Number of items to limit search results to. Will not apply at all to legacy
    860+
    searches.
    861+
    847862
    ### searchstaleness
    848863

    849864
    * Default: 900 (15 minutes)
    850865
    * Type: Number
    851866

    852-
    The age of the cache, in seconds, before another registry request is made.
    867+
    The age of the cache, in seconds, before another registry request is made if
    868+
    using legacy search endpoint.
    853869

    854870
    ### send-metrics
    855871

    ‎deps/npm/doc/misc/npm-scope.md‎

    Lines changed: 21 additions & 15 deletions
    Original file line numberDiff line numberDiff line change
    @@ -4,30 +4,35 @@ npm-scope(7) -- Scoped packages
    44
    ## DESCRIPTION
    55

    66
    All npm packages have a name. Some package names also have a scope. A scope
    7-
    follows the usual rules for package names (url-safe characters, no leading dots
    8-
    or underscores). When used in package names, preceded by an @-symbol and
    9-
    followed by a slash, e.g.
    7+
    follows the usual rules for package names (URL-safe characters, no leading dots
    8+
    or underscores). When used in package names, scopes are preceded by an `@` symbol
    9+
    and followed by a slash, e.g.
    1010

    1111
    @somescope/somepackagename
    1212

    1313
    Scopes are a way of grouping related packages together, and also affect a few
    1414
    things about the way npm treats the package.
    1515

    16+
    Each npm user/organization has their own scope, and only you can add packages
    17+
    in your scope. This means you don't have to worry about someone taking your
    18+
    package name ahead of you. Thus it is also a good way to signal official packages
    19+
    for organizations.
    20+
    1621
    Scoped packages can be published and installed as of `npm@2` and are supported
    17-
    by the primary npm registry. The npm client is backwards-compatible with
    18-
    un-scoped registries, so it can be used to work with scoped and un-scoped
    19-
    registries at the same time.
    22+
    by the primary npm registry. Unscoped packages can depend on scoped packages and
    23+
    vice versa. The npm client is backwards-compatible with unscoped registries,
    24+
    so it can be used to work with scoped and unscoped registries at the same time.
    2025

    2126
    ## Installing scoped packages
    2227

    2328
    Scoped packages are installed to a sub-folder of the regular installation
    2429
    folder, e.g. if your other packages are installed in `node_modules/packagename`,
    25-
    scoped modules will be in `node_modules/@myorg/packagename`. The scope folder
    26-
    (`@myorg`) is simply the name of the scope preceded by an @-symbol, and can
    30+
    scoped modules will be installed in `node_modules/@myorg/packagename`. The scope
    31+
    folder (`@myorg`) is simply the name of the scope preceded by an `@` symbol, and can
    2732
    contain any number of scoped packages.
    2833

    2934
    A scoped package is installed by referencing it by name, preceded by an
    30-
    @-symbol, in `npm install`:
    35+
    `@` symbol, in `npm install`:
    3136

    3237
    npm install @myorg/mypackage
    3338

    @@ -37,7 +42,7 @@ Or in `package.json`:
    3742
    "@myorg/mypackage": "^1.3.0"
    3843
    }
    3944

    40-
    Note that if the @-symbol is omitted in either case npm will instead attempt to
    45+
    Note that if the `@` symbol is omitted, in either case, npm will instead attempt to
    4146
    install from GitHub; see `npm-install(1)`.
    4247

    4348
    ## Requiring scoped packages
    @@ -47,8 +52,8 @@ include the name of the scope when requiring them in your code, e.g.
    4752

    4853
    require('@myorg/mypackage')
    4954

    50-
    There is nothing special about the way Node treats scope folders, this is
    51-
    just specifying to require the module `mypackage` in the folder called `@myorg`.
    55+
    There is nothing special about the way Node treats scope folders. This
    56+
    simply requires the `mypackage` module in the folder named `@myorg`.
    5257

    5358
    ## Publishing scoped packages
    5459

    @@ -57,14 +62,14 @@ published to any registry that supports them, including the primary npm
    5762
    registry.
    5863

    5964
    (As of 2015-04-19, and with npm 2.0 or better, the primary npm registry
    60-
    **does** support scoped packages)
    65+
    **does** support scoped packages.)
    6166

    6267
    If you wish, you may associate a scope with a registry; see below.
    6368

    6469
    ### Publishing public scoped packages to the primary npm registry
    6570

    6671
    To publish a public scoped package, you must specify `--access public` with
    67-
    the initial publication. This will publish the package and set access
    72+
    the initial publication. This will publish the package and set access
    6873
    to `public` as if you had run `npm access public` after publishing.
    6974

    7075
    ### Publishing private scoped packages to the npm registry
    @@ -75,7 +80,7 @@ account.
    7580

    7681
    You can then publish the module with `npm publish` or `npm publish
    7782
    --access restricted`, and it will be present in the npm registry, with
    78-
    restricted access. You can then change the access permissions, if
    83+
    restricted access. You can then change the access permissions, if
    7984
    desired, with `npm access` or on the npmjs.com website.
    8085

    8186
    ## Associating a scope with a registry
    @@ -105,3 +110,4 @@ that registry instead.
    105110
    * npm-install(1)
    106111
    * npm-publish(1)
    107112
    * npm-access(1)
    113+
    * npm-registry(7)

    ‎deps/npm/html/doc/README.html‎

    Lines changed: 4 additions & 4 deletions
    Original file line numberDiff line numberDiff line change
    @@ -15,8 +15,8 @@ <h2 id="synopsis">SYNOPSIS</h2>
    1515
    <p>This is just enough info to get you up and running.</p>
    1616
    <p>Much more info available via <code>npm help</code> once it&#39;s installed.</p>
    1717
    <h2 id="important">IMPORTANT</h2>
    18-
    <p><strong>You need node v0.10 or higher to run this program.</strong></p>
    19-
    <p>To install an old <strong>and unsupported</strong> version of npm that works on node 0.3
    18+
    <p><strong>You need node v4 or higher to run this program.</strong></p>
    19+
    <p>To install an old <strong>and unsupported</strong> version of npm that works on node v0.12
    2020
    and prior, clone the git repo and dig through the old tags and branches.</p>
    2121
    <p><strong>npm is configured to use npm, Inc.&#39;s public package registry at
    2222
    <a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default.</strong></p>
    @@ -60,7 +60,7 @@ <h2 id="windows-install-or-upgrade">Windows Install or Upgrade</h2>
    6060
    <p>Many improvements for Windows users have been made in npm 3 - you will have a better
    6161
    experience if you run a recent version of npm. To upgrade, either use <a href="https://github.com/felixrieseberg/npm-windows-upgrade">Microsoft&#39;s
    6262
    upgrade tool</a>,
    63-
    <a href="http://nodejs.org/download/">download a new version of Node</a>,
    63+
    <a href="https://nodejs.org/en/download/">download a new version of Node</a>,
    6464
    or follow the Windows upgrade instructions in the
    6565
    <a href="https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows">npm Troubleshooting Guide</a>.</p>
    6666
    <p>If that&#39;s not fancy enough for you, then you can fetch the code with
    @@ -126,5 +126,5 @@ <h2 id="see-also">SEE ALSO</h2>
    126126
    <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
    127127
    <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
    128128
    </table>
    129-
    <p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@4.1.2</p>
    129+
    <p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@4.2.0</p>
    130130

    ‎deps/npm/html/doc/cli/npm-access.html‎

    Lines changed: 1 addition & 1 deletion
    < 92D div class="border position-relative rounded-bottom-2">
    Original file line numberDiff line numberDiff line change
    @@ -84,5 +84,5 @@ <h2 id="see-also">SEE ALSO</h2>
    8484
    <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
    8585
    <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
    8686
    </table>
    87-
    <p id="footer">npm-access &mdash; npm@4.1.2</p>
    87+
    <p id="footer">npm-access &mdash; npm@4.2.0</p>
    8888

    0 commit comments

    Comments
     (0)
    0