deps: upgrade npm to 5.3.0
PR-URL: https://github.com/nodejs/node/pull/14235 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
Kat Marchán
James M Snell
parent
fa73087fcf
commit
24f43903b4
1
deps/npm/.github/CODEOWNERS
vendored
Normal file
1
deps/npm/.github/CODEOWNERS
vendored
Normal file
@ -0,0 +1 @@
|
||||
* @npm/cli-team
|
||||
22
deps/npm/.travis.yml
vendored
22
deps/npm/.travis.yml
vendored
@ -22,6 +22,9 @@ matrix:
|
||||
# then master
|
||||
- node_js: "8"
|
||||
env: DEPLOY_VERSION=testing
|
||||
script:
|
||||
- "standard"
|
||||
- "node . run tap -- \"test/tap/*.js\" \"test/broken-under-nyc/*.js\""
|
||||
before_install:
|
||||
# required by test/tap/registry.js
|
||||
- "mkdir -p /var/run/couchdb"
|
||||
@ -29,25 +32,8 @@ notifications:
|
||||
slack: npm-inc:kRqQjto7YbINqHPb1X6nS3g8
|
||||
cache:
|
||||
directories:
|
||||
- $HOME/.npm
|
||||
- html/doc
|
||||
- man
|
||||
- node_modules/.bin
|
||||
- node_modules/.cache
|
||||
- node_modules/deep-equal
|
||||
- node_modules/marked
|
||||
- node_modules/marked-man
|
||||
- node_modules/npm-registry-couchapp
|
||||
- node_modules/npm-registry-mock
|
||||
- node_modules/require-inject
|
||||
- node_modules/sprintf-js
|
||||
- node_modules/standard
|
||||
- node_modules/tacks
|
||||
- node_modules/tap
|
||||
install:
|
||||
- "node . rebuild --depth=0"
|
||||
- "node . install --ignore-scripts"
|
||||
- "node . prune"
|
||||
- "make -j4 doc"
|
||||
- "node . install"
|
||||
script:
|
||||
- "node . run tap -- \"test/tap/*.js\" \"test/broken-under-nyc/*.js\""
|
||||
|
||||
28
deps/npm/AUTHORS
vendored
28
deps/npm/AUTHORS
vendored
@ -475,3 +475,31 @@ Jason Wohlgemuth <jhwohlgemuth@users.noreply.github.com>
|
||||
Ryan Graham <r.m.graham@gmail.com>
|
||||
Hirse <jan.pilzer@gmx.de>
|
||||
Colin Rotherham <work@colinr.com>
|
||||
Aki <hi@akiro.se>
|
||||
Emily Marigold Klassen <forivall@gmail.com>
|
||||
Ramana Venkata <idlike2dream@gmail.com>
|
||||
kierendixon <knitesoulja@hotmail.com>
|
||||
Rácz Tibor Zoltán <racztiborzoltan@gmail.com>
|
||||
Guangcong Luo <guangcongluo@gmail.com>
|
||||
Steven <steven@ceriously.com>
|
||||
Jan Pilzer <jan.pilzer@gmx.de>
|
||||
Leonard Martin <leonard.martin@gmail.com>
|
||||
Teddy Katz <teddy.katz@gmail.com>
|
||||
Simon Legg <leggsimon@gmail.com>
|
||||
Kin Lum <kenneth.kin.lum@gmail.com>
|
||||
dax <guido.dassori@gmail.com>
|
||||
Jože Mlakar <JozeM@ixtlan-team.si>
|
||||
happylynx <happylynx@users.noreply.github.com>
|
||||
Dominic Watson <intellix@users.noreply.github.com>
|
||||
Enrico Weigelt, metux IT consult <enrico.weigelt@gr13.net>
|
||||
Brian Beck <exogen@gmail.com>
|
||||
Ramana Venkata <vramana@users.noreply.github.com>
|
||||
mmkal <misha.kaletsky@gmail.com>
|
||||
Andrew Schmadel <schmod@users.noreply.github.com>
|
||||
AJ Jordan <alex@strugee.net>
|
||||
Mark Banner <standard8@mozilla.com>
|
||||
Richard Simko <richardsimko@users.noreply.github.com>
|
||||
Sanketh Katta <sankethkatta@gmail.com>
|
||||
Tim Needham <tim.needham@wmfs.net>
|
||||
leonardo rojas <leonardo.rojas@shopify.com>
|
||||
Mark Peter Fejes <fejes.mark@gmail.com>
|
||||
|
||||
37
deps/npm/BROKEN.org
vendored
37
deps/npm/BROKEN.org
vendored
@ -1,37 +0,0 @@
|
||||
* Broken test files
|
||||
* add-remote-git-get-resolved.js (needs porting to pacote)
|
||||
* bugs.js (I think because opts.fullMetadata)
|
||||
* builtin-config.js (freezes)
|
||||
* check-cpu-reqs.js (uhhh? it's not checking?)
|
||||
* check-engine-reqs.js (same?)
|
||||
* check-os-reqs.js (same?)
|
||||
* doctor.js (needs rewrite)
|
||||
* full-warning-messages.js
|
||||
* get.js
|
||||
* git-npmignore.js
|
||||
* git-races.js
|
||||
* github-shortcut.js
|
||||
* ignore-shrinkwrap.js
|
||||
* install-shrinkwrapped-git.js
|
||||
* install-with-dev-dep-duplicate.js
|
||||
* legacy-npm-self-install.js (one check failed)
|
||||
* ls-depth-cli.js
|
||||
* outdated-local.js
|
||||
* outdated-notarget.js
|
||||
* outdated-private.js
|
||||
* peer-deps-invalid.js
|
||||
* peer-deps-toplevel.js
|
||||
* peer-deps-without-package-json.js
|
||||
* repo.js
|
||||
* retry-on-stale-cache.js
|
||||
* scope-header.js
|
||||
* shrinkwrap-default-arg-ver.js
|
||||
* shrinkwrap-local-dependency.js
|
||||
* shrinkwrap-optional-dependency.js
|
||||
* shrinkwrap-optional-property.js
|
||||
* shrinkwrap-prod-dependency.js
|
||||
* shrinkwrap-shared-dev-dependency.js
|
||||
* splat-with-only-prerelease-to-latest.js
|
||||
* url-dependencies.js
|
||||
* verify-no-lifecycle-on-repo.js
|
||||
* network/legacy-shrinkwrap.js
|
||||
494
deps/npm/CHANGELOG.md
vendored
494
deps/npm/CHANGELOG.md
vendored
@ -1,3 +1,497 @@
|
||||
## v5.3.0 (2017-07-12):
|
||||
|
||||
As mentioned before, we're continuing to do relatively rapid, smaller releases
|
||||
as we keep working on stomping out `npm@5` issues! We've made a lot of progress
|
||||
since 5.0 already, and this release is no exception.
|
||||
|
||||
### FEATURES
|
||||
|
||||
* [`1e3a46944`](https://github.com/npm/npm/commit/1e3a469448b5db8376e6f64022c4c0c78cdb1686)
|
||||
[#17616](https://github.com/npm/npm/pull/17616)
|
||||
Add `--link` filter option to `npm ls`.
|
||||
([@richardsimko](https://github.com/richardsimko))
|
||||
* [`33df0aaa`](https://github.com/npm/npm/commit/33df0aaaa7271dac982b86f2701d10152c4177c8)
|
||||
`libnpx@9.2.0`:
|
||||
* 4 new languages - Czech, Italian, Turkish, and Chinese (Traditional)! This means npx is available in 14 different languages!
|
||||
* New --node-arg option lets you pass CLI arguments directly to node when the target binary is found to be a Node.js script.
|
||||
([@zkat](https://github.com/zkat))
|
||||
|
||||
### BUGFIXES
|
||||
|
||||
* [`33df0aaa`](https://github.com/npm/npm/commit/33df0aaaa7271dac982b86f2701d10152c4177c8)
|
||||
`libnpx@9.2.0`:
|
||||
* npx should now work on (most) Windows installs. A couple of issues remain.
|
||||
* Prevent auto-fallback from going into an infinite loop when npx disappears.
|
||||
* `npx npx npx npx npx npx npx npx` works again.
|
||||
* `update-notifier` will no longer run for the npx bundled with npm.
|
||||
* `npx <cmd>` in a subdirectory of your project should be able to find your `node_modules/.bin` now. Oops
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`8e979bf80`](https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f08443e26cfc5e64)
|
||||
Revert change where npm stopped flattening modules that required peerDeps.
|
||||
This caused problems because folks were using peer deps to indicate that the
|
||||
target of the peer dep needed to be able to require the dependency and had
|
||||
been relying on the fact that peer deps didn't change the shape of the tree
|
||||
(as of npm@3).
|
||||
The fix that will actually work for people is for a peer dep to insist on
|
||||
never being installed deeper than the the thing it relies on. At the moment
|
||||
this is tricky because the thing the peer dep relies on may not yet have
|
||||
been added to the tree, so we don't know where it is.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`7f28a77f3`](https://github.com/npm/npm/commit/7f28a77f33ef501065f22e8d5e8cffee3195dccd)
|
||||
[#17733](https://github.com/npm/npm/pull/17733)
|
||||
Split remove and unbuild actions into two to get uninstall lifecycles and the
|
||||
removal of transitive symlinks during uninstallation to run in the right
|
||||
order.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`637f2548f`](https://github.com/npm/npm/commit/637f2548facae011eebf5e5c38bfe56a6c2db9fa)
|
||||
[#17748](https://github.com/npm/npm/pull/17748)
|
||||
When rolling back use symlink project-relative path, fixing some issues with
|
||||
`fs-vacuum` getting confused while removing symlinked things.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`f153b5b22`](https://github.com/npm/npm/commit/f153b5b22f647d4d403f5b8cecd2ce63ac75b07c)
|
||||
[#17706](https://github.com/npm/npm/pull/17706)
|
||||
Use semver to compare node versions in npm doctor instead of plain `>`
|
||||
comparison.
|
||||
([@leo-shopify](https://github.com/leo-shopify))
|
||||
* [`542f7561`](https://github.com/npm/npm/commit/542f7561d173eca40eb8d838a16a0ed582fef989)
|
||||
[#17742](https://github.com/npm/npm/pull/17742)
|
||||
Fix issue where `npm version` would sometimes not commit package-locks.
|
||||
([@markpeterfejes](https://github.com/markpeterfejes))
|
||||
* [`51a9e63d`](https://github.com/npm/npm/commit/51a9e63d31cb5ac52259dcf1c364004286072426)
|
||||
[#17777](https://github.com/npm/npm/pull/17777)
|
||||
Fix bug exposed by other bugfixes where the wrong package would be removed.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
### DOCUMENTATION
|
||||
|
||||
Have we mentioned we really like documentation patches? Keep sending them in!
|
||||
Small patches are just fine, and they're a great way to get started contributing
|
||||
to npm!
|
||||
|
||||
* [`fb42d55a9`](https://github.com/npm/npm/commit/fb42d55a9a97afa5ab7db38b3b99088cf68684ea)
|
||||
[#17728](https://github.com/npm/npm/pull/17728)
|
||||
Document semver git urls in package.json docs.
|
||||
([@sankethkatta](https://github.com/sankethkatta))
|
||||
* [`f398c700f`](https://github.com/npm/npm/commit/f398c700fb0f2f3665ebf45995a910ad16cd8d05)
|
||||
[#17684](https://github.com/npm/npm/pull/17684)
|
||||
Tweak heading hierarchy in package.json docs.
|
||||
([@sonicdoe](https://github.com/sonicdoe))
|
||||
* [`d5ad65e50`](https://github.com/npm/npm/commit/d5ad65e50a573cdf9df4155225e869cd6c88ca5e)
|
||||
[#17691](https://github.com/npm/npm/pull/17691)
|
||||
Explicitly document `--no-save` flag for uninstall.
|
||||
([@timneedham](https://github.com/timneedham))
|
||||
|
||||
## v5.2.0 (2017-07-05):
|
||||
|
||||
It's only been a couple of days but we've got some bug fixes we wanted to
|
||||
get out to you all. We also believe that
|
||||
[`npx`](https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b) is ready to be bundled
|
||||
with npm, which we're really excited about!
|
||||
|
||||
### npx!!!
|
||||
|
||||
npx is a tool intended to help round out the experience of using packages
|
||||
from the npm registry — the same way npm makes it super easy to install and
|
||||
manage dependencies hosted on the registry, npx is meant to make it easy to
|
||||
use CLI tools and other executables hosted on the registry. It greatly
|
||||
simplifies a number of things that, until now, required a bit of ceremony to
|
||||
do with plain npm.
|
||||
|
||||
|
||||
|
||||
[@zkat](https://github.com/zkat) has a [great introduction post to npx](https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b)
|
||||
that I highly recommend you give a read
|
||||
|
||||
* [`fb040bee0`](https://github.com/npm/npm/commit/fb040bee0710759c60e45bf8fa2a3b8ddcf4212a)
|
||||
[#17685](https://github.com/npm/npm/pull/17685)
|
||||
Bundle npx with npm itself.
|
||||
([@zkat](https://github.com/zkat))
|
||||
|
||||
### BUG FIXES
|
||||
|
||||
* [`9fe905c39`](https://github.com/npm/npm/commit/9fe905c399d07a3c00c7b22035ddb6b7762731e6)
|
||||
[#17652](https://github.com/npm/npm/pull/17652)
|
||||
Fix max callstack exceeded loops with trees with circular links.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`c0a289b1b`](https://github.com/npm/npm/commit/c0a289b1ba6b99652c43a955b23acbf1de0b56ae)
|
||||
[#17606](https://github.com/npm/npm/pull/17606)
|
||||
Make sure that when write package.json and package-lock.json we always use unix path separators.
|
||||
([@Standard8](https://github.com/Standard8))
|
||||
* [`1658b79ca`](https://github.com/npm/npm/commit/1658b79cad89ccece5ae5ce3c2f691d44b933116)
|
||||
[#17654](https://github.com/npm/npm/pull/17654)
|
||||
Make `npm outdated` show results for globals again. Previously it never thought they were out of date.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`06c154fd6`](https://github.com/npm/npm/commit/06c154fd653d18725d2e760ba825d43cdd807420)
|
||||
[#17678](https://github.com/npm/npm/pull/17678)
|
||||
Stop flattening modules that have peer dependencies. We're making this
|
||||
change to support scenarios where the module requiring a peer dependency
|
||||
is flattened but the peer dependency itself is not, due to conflicts. In
|
||||
those cases the module requiring the peer dep can't be flattened past the
|
||||
location its peer dep was placed in. This initial fix is naive, never
|
||||
flattening peer deps, and we can look into doing something more
|
||||
sophisticated later on.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`88aafee8b`](https://github.com/npm/npm/commit/88aafee8b5b232b7eeb5690279a098d056575791)
|
||||
[#17677](https://github.com/npm/npm/pull/17677)
|
||||
There was an issue where updating a flattened dependency would sometimes
|
||||
unflatten it. This only happened when the dependency had dependencies
|
||||
that in turn required the original dependency.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`b58ec8eab`](https://github.com/npm/npm/commit/b58ec8eab3b4141e7f1b8b42d8cc24f716a804d8)
|
||||
[#17626](https://github.com/npm/npm/pull/17626)
|
||||
Integrators who were building their own copies of npm ran into issues because
|
||||
`make install` and https://npmjs.com/install.sh weren't aware that
|
||||
`npm install` creates links now when given a directory to work on. This does not impact folks
|
||||
installing npm with `npm install -g npm`.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
### DOC FIXES
|
||||
|
||||
* [`10bef735e`](https://github.com/npm/npm/commit/10bef735e825acc8278827d34df415dfcd8c67d4)
|
||||
[#17645](https://github.com/npm/npm/pull/17645)
|
||||
Fix some github issue links in the 5.1.0 changelog
|
||||
([@schmod](https://github.com/schmod))
|
||||
* [`85fa9dcb2`](https://github.com/npm/npm/commit/85fa9dcb2f0b4f51b515358e0184ec82a5845227)
|
||||
[#17634](https://github.com/npm/npm/pull/17634)
|
||||
Fix typo in package-lock docs.
|
||||
([@sonicdoe](https://github.com/sonicdoe))
|
||||
* [`688699bef`](https://github.com/npm/npm/commit/688699befc2d147288c69a9405fb8354ecaebe36)
|
||||
[#17628](https://github.com/npm/npm/pull/17628)
|
||||
Recommend that folks looking for support join us on https://package.community/ or message
|
||||
[@npm_support](https://twitter.com/npm_support) on Twitter.
|
||||
([@strugee](https://github.com/strugee))
|
||||
|
||||
|
||||
## v5.1.0 (2017-07-05):
|
||||
|
||||
Hey y'all~
|
||||
|
||||
We've got some goodies for you here, including `npm@5`'s first semver-minor
|
||||
release! This version includes a huge number of fixes, particularly for some of
|
||||
the critical bugs users were running into after upgrading npm. You should
|
||||
overall see a much more stable experience, and we're going to continue hacking
|
||||
on fixes for the time being. Semver-major releases, specially for tools like
|
||||
npm, are bound to cause some instability, and getting `npm@5` stable is the CLI
|
||||
team's top priority for now!
|
||||
|
||||
Not that bugfixes are the only things that landed, either: between improvements
|
||||
that fell out of the bugfixes, and some really cool work by community members
|
||||
like [@mikesherov](https://github.com/mikesherov), `npm@5.1.0` is **_twice as
|
||||
fast_** as `npm@5.0.0` in some benchmarks. We're not stopping there, either: you
|
||||
can expect a steady stream of speed improvements over the course of the year.
|
||||
It's not _top_ priority, but we'll keep doing what we can to make sure npm saves
|
||||
its users as much time as possible.
|
||||
|
||||
Hang on to your seats. At **100 commits**, this release is a bit of a doozy. 😎
|
||||
|
||||
### FEATURES
|
||||
|
||||
Semver-minor releases, of course, mean that there's a new feature somewhere,
|
||||
right? Here's what's bumping that number for us this time:
|
||||
|
||||
* [`a09c1a69d`](https://github.com/npm/npm/commit/a09c1a69df05b753464cc1272cdccc6af0f4da5a)
|
||||
[#16687](https://github.com/npm/npm/pull/16687)
|
||||
Allow customizing the shell used to execute `run-script`s.
|
||||
([@mmkal](https://github.com/mmkal))
|
||||
* [`4f45ba222`](https://github.com/npm/npm/commit/4f45ba222e2ac6dbe6d696cb7a8e678bbda7c839) [`a48958598`](https://github.com/npm/npm/commit/a489585985540deed4edc03418636c9e97aa9e40) [`901bef0e1`](https://github.com/npm/npm/commit/901bef0e1ea806fc08d8d58744a9f813b6c020ab)
|
||||
[#17508](https://github.com/npm/npm/pull/17508)
|
||||
Add a new `requires` field to `package-lock.json` with information about the
|
||||
_logical_ dependency tree. This includes references to the specific version
|
||||
each package is intended to see, and can be used for many things, such as
|
||||
[converting `package-lock.json` to other lockfile
|
||||
formats](https://twitter.com/maybekatz/status/880578566907248640), various
|
||||
optimizations, and verifying correctness of a package tree.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`47e8fc8eb`](https://github.com/npm/npm/commit/47e8fc8eb9b5faccef9e03ab991cf37458c16249)
|
||||
[#17508](https://github.com/npm/npm/pull/17508)
|
||||
Make `npm ls` take package locks (and shrinkwraps) into account. This means
|
||||
`npm ls` can now be used to see [which dependencies are
|
||||
missing](https://twitter.com/maybekatz/status/880446509547794437), so long as
|
||||
a package lock has been previously generated with it in.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`f0075e7ca`](https://github.com/npm/npm/commit/f0075e7caa3e151424a254d7809ae4489ed8df90)
|
||||
[#17508](https://github.com/npm/npm/pull/17508)
|
||||
Take `package.json` changes into account when running installs -- if you
|
||||
remove or add a dependency to `package.json` manually, npm will now pick that
|
||||
up and update your tree and package lock accordingly.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`83a5455aa`](https://github.com/npm/npm/commit/83a5455aac3c5cc2511ab504923b652b13bd66a0)
|
||||
[#17205](https://github.com/npm/npm/pull/17205)
|
||||
Add `npm udpate` as an alias for `npm update`, for symmetry with
|
||||
`install`/`isntall`.
|
||||
([@gdassori](https://github.com/gdassori))
|
||||
* [`57225d394`](https://github.com/npm/npm/commit/57225d394b6174eb0be48393d8e18da0991f67b6)
|
||||
[#17120](https://github.com/npm/npm/pull/17120)
|
||||
npm will no longer warn about `preferGlobal`, and the option is now
|
||||
deprecated.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`82df7bb16`](https://github.com/npm/npm/commit/82df7bb16fc29c47a024db4a8c393e55f883744b)
|
||||
[#17351](https://github.com/npm/npm/pull/17351)
|
||||
As some of you may already know `npm build` doesn't do what a lot of people
|
||||
expect: It's mainly an npm plumbing command, and is part of the more familiar
|
||||
`npm rebuild` command. That said, a lot of users assume that this is the way
|
||||
to run an npm `run-script` named `build`, which is an incredibly common script
|
||||
name to use. To clarify things for users, and encourage them to use `npm run
|
||||
build` instead, npm will now warn if `npm build` is run without any arguments.
|
||||
([@lennym](https://github.com/lennym))
|
||||
|
||||
### PERFORMANCE
|
||||
|
||||
* [`59f86ef90`](https://github.com/npm/npm/commit/59f86ef90a58d8dc925c9613f1c96e68bee5ec7b) [`43be9d222`](https://github.com/npm/npm/commit/43be9d2222b23ebb0a427ed91824ae217e6d077a) [`e906cdd98`](https://github.com/npm/npm/commit/e906cdd980b4722e66618ce295c682b9a8ffaf8f)
|
||||
[#16633](https://github.com/npm/npm/pull/16633)
|
||||
npm now parallelizes tarball extraction across multiple child process workers.
|
||||
This can significantly speed up installations, specially when installing from
|
||||
cache, and will improve with number of processors.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`e0849878d`](https://github.com/npm/npm/commit/e0849878dd248de8988c2ef3fc941054625712ca)
|
||||
[#17441](https://github.com/npm/npm/pull/17441)
|
||||
Avoid building environment for empty lifecycle scripts. This change alone
|
||||
accounted for as much as a 15% speed boost for npm installations by outright
|
||||
skipping entire steps of the installer when not needed.
|
||||
([@mikesherov](https://github.com/mikesherov))
|
||||
* [`265c2544c`](https://github.com/npm/npm/commit/265c2544c8ded10854909243482e6437ed03c261)
|
||||
[npm/hosted-git-info#24](https://github.com/npm/hosted-git-info/pull/24)
|
||||
`hosted-git-info@2.5.0`: Add caching to `fromURL`, which gets called many,
|
||||
many times by the installer. This improved installation performance by around
|
||||
10% on realistic application repositories.
|
||||
([@mikesherov](https://github.com/mikesherov))
|
||||
* [`901d26cb`](https://github.com/npm/npm/commit/901d26cb656e7e773d9a38ef4eac9263b95e07c8)
|
||||
[npm/read-package-json#20](https://github.com/npm/read-package-json/pull/70)
|
||||
`read-package-json@2.0.9`: Speed up installs by as much as 20% by
|
||||
reintroducing a previously-removed cache and making it actually be correct
|
||||
this time around.
|
||||
([@mikesherov](https://github.com/mikesherov))
|
||||
* [`44e37045d`](https://github.com/npm/npm/commit/44e37045d77bc40adf339b423d42bf5e9b4d4d91)
|
||||
Eliminate `Bluebird.promisifyAll` from our codebase.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`3b4681b53`](https://github.com/npm/npm/commit/3b4681b53db7757985223932072875d099694677)
|
||||
[#17508](https://github.com/npm/npm/pull/17508)
|
||||
Stop calling `addBundle` on locked deps, speeding up the
|
||||
`package-lock.json`-based fast path.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
### BUGFIXES
|
||||
|
||||
* [#17508](https://github.com/npm/npm/pull/17508)
|
||||
This is a big PR that fixes a variety of issues when installing from package
|
||||
locks. If you were previously having issues with missing dependencies or
|
||||
unwanted removals, this might have fixed it:
|
||||
* It introduces a new `package-lock.json` field, called `requires`, which tracks which modules a given module requires.
|
||||
* It fixes [#16839](https://github.com/npm/npm/issues/16839) which was caused by not having this information available, particularly when git dependencies were involved.
|
||||
* It fixes [#16866](https://github.com/npm/npm/issues/16866), allowing the `package.json` to trump the `package-lock.json`.
|
||||
* `npm ls` now loads the shrinkwrap, which opens the door to showing a full tree of dependencies even when nothing is yet installed. (It doesn't do that yet though.)
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`656544c31`](https://github.com/npm/npm/commit/656544c31cdef3cef64fc10c24f03a8ae2685e35) [`d21ab57c3`](https://github.com/npm/npm/commit/d21ab57c3ef4f01d41fb6c2103debe884a17dc22)
|
||||
[#16637](https://github.com/npm/npm/pull/16637)
|
||||
Fix some cases where `npm prune` was leaving some dependencies unpruned if
|
||||
to-be-pruned dependencies depended on them.
|
||||
([@exogen](https://github.com/exogen))
|
||||
* [`394436b09`](https://github.com/npm/npm/commit/394436b098dcca2d252061f95c4eeb92c4a7027c)
|
||||
[#17552](https://github.com/npm/npm/pull/17552)
|
||||
Make `refresh-package-json` re-verify the package platform. This fixes an
|
||||
issue most notably experienced by Windows users using `create-react-app` where
|
||||
`fsevents` would not short-circuit and cause a crash during its
|
||||
otherwise-skipped native build phase.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`9e5a94354`](https://github.com/npm/npm/commit/9e5a943547b29c8d022192afd9398b3a136a7e5a)
|
||||
[#17590](https://github.com/npm/npm/pull/17590)
|
||||
Fix an issue where `npm@5` would crash when trying to remove packages
|
||||
installed with `npm@<5`.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`c3b586aaf`](https://github.com/npm/npm/commit/c3b586aafa9eabac572eb6e2b8a7266536dbc65b)
|
||||
[#17141](https://github.com/npm/npm/issues/17141)
|
||||
Don't update the package.json when modifying packages that don't go there.
|
||||
This was previously causing `package.json` to get a `"false": {}` field added.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`d04a23de2`](https://github.com/npm/npm/commit/d04a23de21dd9991b32029d839b71e10e07b400d) [`4a5b360d5`](https://github.com/npm/npm/commit/4a5b360d561f565703024085da0927ccafe8793e) [`d9e53db48`](https://github.com/npm/npm/commit/d9e53db48ca227b21bb67df48c9b3580cb390e9e)
|
||||
`pacote@2.7.38`:
|
||||
* [zkat/pacote#102](https://github.com/zkat/pacote/pull/102) Fix issue with tar extraction and special characters.
|
||||
* Enable loose semver parsing in some missing corner cases.
|
||||
([@colinrotherham](https://github.com/colinrotherham), [@zkat](https://github.com/zkat), [@mcibique](https://github.com/mcibique))
|
||||
* [`e2f815f87`](https://github.com/npm/npm/commit/e2f815f87676b7c50b896e939cee15a01aa976e4)
|
||||
[#17104](https://github.com/npm/npm/pull/17104)
|
||||
Write an empty str and wait for flush to exit to reduce issues with npm
|
||||
exiting before all output is complete when it's a child process.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`835fcec60`](https://github.com/npm/npm/commit/835fcec601204971083aa3a281c3a9da6061a7c2)
|
||||
[#17060](https://github.com/npm/npm/pull/17060)
|
||||
Make git repos with prepare scripts always install with both dev and prod
|
||||
flags.
|
||||
([@intellix](https://github.com/intellix))
|
||||
* [`f1dc8a175`](https://github.com/npm/npm/commit/f1dc8a175eed56f1ed23bd5773e5e10beaf6cb31)
|
||||
[#16879](https://github.com/npm/npm/pull/16879)
|
||||
Fix support for `always-auth` and `_auth`. They are now both available in both
|
||||
unscoped and registry-scoped configurations.
|
||||
([@jozemlakar](https://github.com/jozemlakar))
|
||||
* [`ddd8a1ca2`](https://github.com/npm/npm/commit/ddd8a1ca2fa3377199af74ede9d0c1a406d19793)
|
||||
Serialize package specs to prevent `[object Object]` showing up in logs during
|
||||
extraction.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`99ef3b52c`](https://github.com/npm/npm/commit/99ef3b52caa7507e87a4257e622f8964b1c1f5f3)
|
||||
[#17505](https://github.com/npm/npm/pull/17505)
|
||||
Stop trying to commit updated `npm-shrinkwrap.json` and `package-lock.json` if
|
||||
they're `.gitignore`d.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`58be2ec59`](https://github.com/npm/npm/commit/58be2ec596dfb0353ad2570e6750e408339f1478)
|
||||
Make sure uid and gid are getting correctly set even when they're `0`. This
|
||||
should fix some Docker-related issues with bad permissions/broken ownership.
|
||||
([@rgrove](https://github.com/rgrove))
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`9d1e3b6fa`](https://github.com/npm/npm/commit/9d1e3b6fa01bb563d76018ee153259d9507658cf)
|
||||
[#17506](https://github.com/npm/npm/pull/17506)
|
||||
Skip writing package.json and locks if on-disk version is identical to the new
|
||||
one.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`3fc6477a8`](https://github.com/npm/npm/commit/3fc6477a89773786e6c43ef43a23e5cdc662ff8e)
|
||||
[#17592](https://github.com/npm/npm/pull/17592)
|
||||
Fix an issue where `npm install -g .` on a package with no `name` field would
|
||||
cause the entire global `node_modules` directory to be replaced with a symlink
|
||||
to `$CWD`. lol.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`06ba0a14a`](https://github.com/npm/npm/commit/06ba0a14a6c1c8cdcc8c062b68c8c63041b0cec0)
|
||||
[#17591](https://github.com/npm/npm/pull/17591)
|
||||
Fix spurious removal reporting: if you tried to remove something that didn't
|
||||
actually exist, npm would tell you it removed 1 package even though there was
|
||||
nothing to do.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`20ff05f8`](https://github.com/npm/npm/commit/20ff05f8fe0ad8c36e1323d30b63b4d2ff7e11ef)
|
||||
[#17629](https://github.com/npm/npm/pull/17629)
|
||||
When removing a link, keep dependencies installed inside of it instead of
|
||||
removing them, if the link is outside the scope of the current project. This
|
||||
fixes an issue where removing globally-linked packages would remove all their
|
||||
dependencies in the source directory, as well as some ergonomic issues when
|
||||
using links in other situations.
|
||||
([@iarna](https://github.com/iarna))
|
||||
|
||||
### DOCS
|
||||
|
||||
* [`fd5fab595`](https://github.com/npm/npm/commit/fd5fab5955a20a9bb8c0e77092ada1435f73a8d2)
|
||||
[#16441](https://github.com/npm/npm/pull/16441)
|
||||
Add spec for `npm-shrinkwrap.json` and `package-lock.json` from RFC.
|
||||
([@iarna](https://github.com/iarna))
|
||||
* [`9589c1ccb`](https://github.com/npm/npm/commit/9589c1ccb3f794abaaa48c2a647ada311dd881ef)
|
||||
[#17451](https://github.com/npm/npm/pull/17451)
|
||||
Fix typo in changelog.
|
||||
([@watilde](https://github.com/watilde))
|
||||
* [`f8e76d856`](https://github.com/npm/npm/commit/f8e76d8566ae1965e57d348df74edad0643b66a6)
|
||||
[#17370](https://github.com/npm/npm/pull/17370)
|
||||
Correct the default prefix config path for Windows operating systems in the
|
||||
documentation for npm folders.
|
||||
([@kierendixon](https://github.com/kierendixon))
|
||||
* [`d0f3b5a12`](https://github.com/npm/npm/commit/d0f3b5a127718b0347c6622a2b9c28341c530d36)
|
||||
[#17369](https://github.com/npm/npm/pull/17369)
|
||||
Fix `npm-config` reference to `userconfig` & `globalconfig` environment
|
||||
variables.
|
||||
([@racztiborzoltan](https://github.com/racztiborzoltan))
|
||||
* [`87629880a`](https://github.com/npm/npm/commit/87629880a71baec352c1b5345bc29268d6212467)
|
||||
[#17336](https://github.com/npm/npm/pull/17336)
|
||||
Remove note in docs about `prepublish` being entirely removed.
|
||||
([@Hirse](https://github.com/Hirse))
|
||||
* [`a1058afd9`](https://github.com/npm/npm/commit/a1058afd9a7a569bd0ac65b86eadd4fe077a7221)
|
||||
[#17169](https://github.com/npm/npm/pull/17169)
|
||||
Document `--no-package-lock` flag.
|
||||
([@leggsimon](https://github.com/leggsimon))
|
||||
* [`32fc6e41a`](https://github.com/npm/npm/commit/32fc6e41a2ce4dbcd5ce1e5f291e2e2efc779d48)
|
||||
[#17250](https://github.com/npm/npm/pull/17250)
|
||||
Fix a typo in the shrinkwrap docs.
|
||||
([@Zarel](https://github.com/Zarel))
|
||||
* [`f19bd3c8c`](https://github.com/npm/npm/commit/f19bd3c8cbd37c8a99487d6b5035282580ac3e9d)
|
||||
[#17249](https://github.com/npm/npm/pull/17249)
|
||||
Fix a package-lock.json cross-reference link.
|
||||
([@not-an-aardvark](https://github.com/not-an-aardvark))
|
||||
* [`153245edc`](https://github.com/npm/npm/commit/153245edc4845db670ada5e95ef384561706a751)
|
||||
[#17075](https://github.com/npm/npm/pull/17075/files)
|
||||
Fix a typo in `npm-config` docs.
|
||||
([@KennethKinLum](https://github.com/KennethKinLum))
|
||||
* [`c9b534a14`](https://github.com/npm/npm/commit/c9b534a148818d1a97787c0dfdba5f64ce3618a6)
|
||||
[#17074](https://github.com/npm/npm/pull/17074)
|
||||
Clarify config documention with multiple boolean flags.
|
||||
([@KennethKinLum](https://github.com/KennethKinLum))
|
||||
* [`e111b0a40`](https://github.com/npm/npm/commit/e111b0a40c4bc6691d7b8d67ddce5419e67bfd27)
|
||||
[#16768](https://github.com/npm/npm/pull/16768)
|
||||
Document the `-l` option to `npm config list`.
|
||||
([@happylynx](https://github.com/happylynx))
|
||||
* [`5a803ebad`](https://github.com/npm/npm/commit/5a803ebadd61229bca3d64fb3ef1981729b2548e)
|
||||
[#16548](https://github.com/npm/npm/pull/16548)
|
||||
Fix permissions for documentation files. Some of them had `+x` set. (???)
|
||||
([@metux](https://github.com/metux))
|
||||
* [`d57d4f48c`](https://github.com/npm/npm/commit/d57d4f48c6cd00fdf1e694eb49e9358071d8e105)
|
||||
[#17319](https://github.com/npm/npm/pull/17319)
|
||||
Document that the `--silent` option for `npm run-script` can be used to
|
||||
suppress `npm ERR!` output on errors.
|
||||
([@styfle](https://github.com/styfle))
|
||||
|
||||
### MISC
|
||||
|
||||
Not all contributions need to be visible features, docs, or bugfixes! It's super
|
||||
helpful when community members go over our code and help clean it up, too!
|
||||
|
||||
* [`9e5b76140`](https://github.com/npm/npm/commit/9e5b76140ffdb7dcd12aa402793644213fb8c5d7)
|
||||
[#17411](https://github.com/npm/npm/pull/17411)
|
||||
Convert all callback-style `move` usage to use Promises.
|
||||
([@vramana](https://github.com/vramana))
|
||||
* [`0711c08f7`](https://github.com/npm/npm/commit/0711c08f779ac641ec42ecc96f604c8861008b28)
|
||||
[#17394](https://github.com/npm/npm/pull/17394)
|
||||
Remove unused argument in `deepSortObject`.
|
||||
([@vramana](https://github.com/vramana))
|
||||
* [`7d650048c`](https://github.com/npm/npm/commit/7d650048c8ed5faa0486492f1eeb698e7383e32f)
|
||||
[#17563](https://github.com/npm/npm/pull/17563)
|
||||
Refactor some code to use `Object.assign`.
|
||||
([@vramana](https://github.com/vramana))
|
||||
* [`993f673f0`](https://github.com/npm/npm/commit/993f673f056aea5f602ea04b1e697b027c267a2d)
|
||||
[#17600](https://github.com/npm/npm/pull/17600)
|
||||
Remove an old comment.
|
||||
([@vramana](https://github.com/vramana))
|
||||
|
||||
## v5.0.4 (2017-06-13):
|
||||
|
||||
Hey y'all. This is another minor patch release with a variety of little fixes
|
||||
we've been accumulating~
|
||||
|
||||
* [`f0a37ace9`](https://github.com/npm/npm/commit/f0a37ace9ab7879cab20f2b0fcd7840bfc305feb)
|
||||
Fix `npm doctor` when hitting registries without `ping`.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`64f0105e8`](https://github.com/npm/npm/commit/64f0105e81352b42b72900d83b437b90afc6d9ce)
|
||||
Fix invalid format error when setting cache-related headers.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`d2969c80e`](https://github.com/npm/npm/commit/d2969c80e4178faebf0f7c4cab6eb610dd953cc6)
|
||||
Fix spurious `EINTEGRITY` issue.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`800cb2b4e`](https://github.com/npm/npm/commit/800cb2b4e2d0bd00b5c9082a896f2110e907eb0b)
|
||||
[#17076](https://github.com/npm/npm/pull/17076)
|
||||
Use legacy `from` field to improve upgrade experience from legacy shrinkwraps
|
||||
and installs.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`4100d47ea`](https://github.com/npm/npm/commit/4100d47ea58b4966c02604f71350b5316108df6a)
|
||||
[#17007](https://github.com/npm/npm/pull/17007)
|
||||
Restore loose semver parsing to match older npm behavior when running into
|
||||
invalid semver ranges in dependencies.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`35316cce2`](https://github.com/npm/npm/commit/35316cce2ca2d8eb94161ec7fe7e8f7bec7b3aa7)
|
||||
[#17005](https://github.com/npm/npm/pull/17005)
|
||||
Emulate npm@4's behavior of simply marking the peerDep as invalid, instead of
|
||||
crashing.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`e7e8ee5c5`](https://github.com/npm/npm/commit/e7e8ee5c57c7238655677e118a8809b652019f53)
|
||||
[#16937](https://github.com/npm/npm/pull/16937)
|
||||
Workaround for separate bug where `requested` was somehow null.
|
||||
([@forivall](https://github.com/forivall))
|
||||
* [`2d9629bb2`](https://github.com/npm/npm/commit/2d9629bb2043cff47eaad2654a64d2cef5725356)
|
||||
Better logging output for git errors.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`2235aea73`](https://github.com/npm/npm/commit/2235aea73569fb9711a06fa6344ef31247177dcd)
|
||||
More scp-url fixes: parsing only worked correctly when a committish was
|
||||
present.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`80c33cf5e`](https://github.com/npm/npm/commit/80c33cf5e6ef207450949764de41ea96538c636e)
|
||||
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.
|
||||
([@zkat](https://github.com/zkat))
|
||||
* [`2b1e40efb`](https://github.com/npm/npm/commit/2b1e40efba0b3d1004259efa4275cf42144e3ce3)
|
||||
Limit shallow cloning to hosts which are known to support it.
|
||||
([@zkat](https://github.com/zkat))
|
||||
|
||||
## v5.0.3 (2017-06-05)
|
||||
|
||||
Happy Monday, y'all! We've got another npm release for you with the fruits of
|
||||
|
||||
8
deps/npm/Makefile
vendored
8
deps/npm/Makefile
vendored
@ -14,7 +14,8 @@ html_docdeps = html/dochead.html \
|
||||
cli_mandocs = $(shell find doc/cli -name '*.md' \
|
||||
|sed 's|.md|.1|g' \
|
||||
|sed 's|doc/cli/|man/man1/|g' ) \
|
||||
man/man1/npm-README.1
|
||||
man/man1/npm-README.1 \
|
||||
man/man1/npx.1
|
||||
|
||||
files_mandocs = $(shell find doc/files -name '*.md' \
|
||||
|sed 's|.md|.5|g' \
|
||||
@ -56,7 +57,7 @@ latest:
|
||||
node bin/npm-cli.js install -g -f npm ${NPMOPTS}
|
||||
|
||||
install: all
|
||||
node bin/npm-cli.js install -g -f ${NPMOPTS}
|
||||
node bin/npm-cli.js install -g -f ${NPMOPTS} $(shell node bin/npm-cli.js pack | tail -1)
|
||||
|
||||
# backwards compat
|
||||
dev: install
|
||||
@ -96,6 +97,9 @@ man/man1/%.1: doc/cli/%.md scripts/doc-build.sh package.json
|
||||
@[ -d man/man1 ] || mkdir -p man/man1
|
||||
scripts/doc-build.sh $< $@
|
||||
|
||||
man/man1/npx.1: node_modules/libnpx/libnpx.1
|
||||
cat $< | sed s/libnpx/npx/ > $@
|
||||
|
||||
man/man5/npm-json.5: man/man5/package.json.5
|
||||
cp $< $@
|
||||
|
||||
|
||||
5
deps/npm/README.md
vendored
5
deps/npm/README.md
vendored
@ -158,8 +158,9 @@ When you find issues, please report them:
|
||||
Be sure to include *all* of the output from the npm command that didn't work
|
||||
as expected. The `npm-debug.log` file is also helpful to provide.
|
||||
|
||||
You can also look for isaacs in #node.js on irc://irc.freenode.net. She
|
||||
will no doubt tell you to put the output in a gist or email.
|
||||
You can also find npm people in `#npm` on https://package.community/ or
|
||||
[on Twitter](https://twitter.com/npm_support). Whoever responds will no
|
||||
doubt tell you to put the output in a gist or email.
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
|
||||
86
deps/npm/TODO.org
vendored
86
deps/npm/TODO.org
vendored
@ -1,86 +0,0 @@
|
||||
* Finished
|
||||
* [COMPLETED] npm: remove packageIntegrity
|
||||
* [COMPLETED] npm: fix lifecycle stuff
|
||||
* pack:
|
||||
* pre-: immediately before tarball contents are packed. Need to re-read package.json immediately after
|
||||
* pack: No pack lifecycle
|
||||
* post-: immediately after tarball reaches its final destination (not immediately after packaging)
|
||||
* prepare: `npm install`, immediately before `postinstall`, and immediately before `prepack`, never if `--prod`, after prepublish, before prepublishOnly
|
||||
* prepublish: alias for `prepare`
|
||||
* prepublishOnly: ONLY on `npm publish` (never on `npm pack`), runs before prepack (which takes care of re-reading package.json), re-reads package.json immediately after
|
||||
* [COMPLETED] pacote: fix always-auth bug
|
||||
* [COMPLETED] pacote: figure out why cache is being written as root
|
||||
* [COMPLETED] npm: make `npm update` save files as the right type
|
||||
* [COMPLETED] npm: update docs with npm5 changes
|
||||
* [COMPLETED] npm: don't write "problems" into package-lock
|
||||
* [COMPLETED] npm: add `created-with`, `shrinkwrap-version`, and `package-integrity`
|
||||
* [COMPLETED] npm: warn on incompatible package-lock version
|
||||
* [COMPLETED] npm: warn if both shrinkwrap and package-lock are there
|
||||
* [COMPLETED] npm: fix git-prepare
|
||||
* [COMPLETED] npm: fix auth failure for locked scoped deps
|
||||
* [COMPLETED] npm: send the user-agent through to pacote
|
||||
* [COMPLETED] npm: get https://github.com/npm/write-file-atomic/pull/23 merged
|
||||
* [COMPLETED] npm: get https://github.com/npm/fstream-npm/pull/27 merged
|
||||
* [COMPLETED] npm: if local deps exist w/o needed metadata, fetch it
|
||||
* [COMPLETED] Run `prepare` during git tarball packing phase
|
||||
* [COMPLETED] npm: put npm cache clear behind --force
|
||||
* [COMPLETED] npm: package-lock.json
|
||||
* lib/install/read-shrinkwrap.js
|
||||
* lib/shrinkwrap.js
|
||||
* lib/install/save.js (?)
|
||||
* lib/utils/tar.js (add autoignore)
|
||||
* fstream-npm (add autoignore)
|
||||
* lib/version.js
|
||||
* [COMPLETED] npm: --save by default
|
||||
* [COMPLETED] npm: make sure `npm i <pkg>` defaults to package.json
|
||||
* it only happens for command line arguments
|
||||
* getAllMetadata
|
||||
* Apparently, I did this way back when and totally forgot. lol.
|
||||
* [COMPLETED] make-fetch-happen: make sure other options npm used are implemented
|
||||
* look at the comment at the bottom of pacote.js
|
||||
* [COMPLETED] make-fetch-happen: support strictSSL option
|
||||
* [COMPLETED] Write npm@5 speeds presentation for Friday
|
||||
* [COMPLETED] pacote: support `opts.fullMetadata` for `pkg.manifest`
|
||||
* [COMPLETED] npm: fix invalid package: null error
|
||||
* [COMPLETED] make-fetch-happen: case-insensitive http_proxy/proxy/https_proxy
|
||||
* [COMPLETED] cacache: integrate cacache@8 into npm/pacote/mfh
|
||||
* [COMPLETED] make-fetch-happen: literally vendor in node-fetch. sigh.
|
||||
* basically, the whole tarball situation prevents shrinkwrap. sux :<
|
||||
* note: solved this by forking node-fetch into node-fetch-npm
|
||||
* [COMPLETED] pacote: http auth and alwaysAuth
|
||||
* https://github.com/zkat/pacote/issues/77
|
||||
* [COMPLETED] make-fetch-happen: NO_PROXY support
|
||||
* https://github.com/zkat/make-fetch-happen/issues/17
|
||||
* [COMPLETED] npm: calculate sri with ssri and add it to dist.integrity
|
||||
* [COMPLETED] pacote: refactor handler API
|
||||
* maybe use Protoduck?
|
||||
* [COMPLETED] npm: nag Ryan about when sha512 is happening
|
||||
* He says it's delayed 😭
|
||||
* I can still start sending integrity in the publish
|
||||
* [COMPLETED] npm: fix bundle replacement issues (see: npm i nyc warning spam)
|
||||
* need fromBundle attribute on shrinkwrap and pass it through. the sw.version && sw.integrity-based fake node needs to have this there.
|
||||
* Backlog
|
||||
* [TODO] make-fetch-happen: integrity failures are being thrown
|
||||
* [TODO] write-file-atomic: review https://github.com/npm/write-file-atomic/pull/22
|
||||
* [TODO] pacote: write tests for git handlers
|
||||
* https://github.com/zkat/pacote/issues/70
|
||||
* [TODO] pacote: offline feature support for git deps
|
||||
* [TODO] npm: get logging working during the recalculateMetadata spam
|
||||
* [TODO] pacote: opts.extraHeaders
|
||||
* https://github.com/zkat/pacote/issues/79
|
||||
* [TODO] pacote: ECONNRESET recovery
|
||||
* https://github.com/zkat/pacote/issues/8
|
||||
* [TODO] pacote: skip node_modules extraction for non-bundleDeps
|
||||
* https://github.com/zkat/pacote/issues/49
|
||||
* [TODO] pacote: write tests for file/directory handlers
|
||||
* [TODO] npm: `npm publish --dry-run` -> https://npm.im/pkgfiles ?
|
||||
* Rebecca says yea
|
||||
* [TODO] make-fetch-happen: write tests for agent pooling/proxy
|
||||
* https://github.com/zkat/make-fetch-happen/issues/16
|
||||
* [TODO] make-fetch-happen: retry notification
|
||||
* https://github.com/zkat/make-fetch-happen/issues/21
|
||||
* [TODO] npm: more informative logging when building git deps
|
||||
* Needed for npm@5
|
||||
* Active
|
||||
* [TODO] npm: figure out https://github.com/npm/npm/issues/16665
|
||||
* [TODO] npm: first-run notice about npm5 still having known issues
|
||||
34
deps/npm/bin/npx
vendored
Normal file
34
deps/npm/bin/npx
vendored
Normal file
@ -0,0 +1,34 @@
|
||||
#!/bin/sh
|
||||
(set -o igncr) 2>/dev/null && set -o igncr; # cygwin encoding fix
|
||||
|
||||
basedir=`dirname "$0"`
|
||||
|
||||
case `uname` in
|
||||
*CYGWIN*) basedir=`cygpath -w "$basedir"`;;
|
||||
esac
|
||||
|
||||
NODE_EXE="$basedir/node.exe"
|
||||
if ! [ -x "$NODE_EXE" ]; then
|
||||
NODE_EXE=node
|
||||
fi
|
||||
|
||||
NPX_CLI_JS="$basedir/node_modules/npm/bin/npx-cli.js"
|
||||
|
||||
case `uname` in
|
||||
*MINGW*)
|
||||
NPM_PREFIX=`"$NODE_EXE" "$NPX_CLI_JS" prefix -g`
|
||||
NPM_PREFIX_NPX_CLI_JS="$NPM_PREFIX/node_modules/npm/bin/npx-cli.js"
|
||||
if [ -f "$NPM_PREFIX_NPX_CLI_JS" ]; then
|
||||
NPX_CLI_JS="$NPM_PREFIX_NPX_CLI_JS"
|
||||
fi
|
||||
;;
|
||||
*CYGWIN*)
|
||||
NPM_PREFIX=`"$NODE_EXE" "$NPX_CLI_JS" prefix -g`
|
||||
NPM_PREFIX_NPX_CLI_JS="$NPM_PREFIX/node_modules/npm/bin/npx-cli.js"
|
||||
if [ -f "$NPM_PREFIX_NPX_CLI_JS" ]; then
|
||||
NPX_CLI_JS="$NPM_PREFIX_NPX_CLI_JS"
|
||||
fi
|
||||
;;
|
||||
esac
|
||||
|
||||
"$NODE_EXE" "$NPX_CLI_JS" "$@"
|
||||
8
deps/npm/bin/npx-cli.js
vendored
Executable file
8
deps/npm/bin/npx-cli.js
vendored
Executable file
@ -0,0 +1,8 @@
|
||||
#!/usr/bin/env node
|
||||
|
||||
const npx = require('libnpx')
|
||||
const path = require('path')
|
||||
|
||||
const NPM_PATH = path.join(__dirname, 'npm-cli.js')
|
||||
|
||||
npx(npx.parseArgs(process.argv, NPM_PATH))
|
||||
19
deps/npm/bin/npx.cmd
vendored
Normal file
19
deps/npm/bin/npx.cmd
vendored
Normal file
@ -0,0 +1,19 @@
|
||||
:: Created by npm, please don't edit manually.
|
||||
@ECHO OFF
|
||||
|
||||
SETLOCAL
|
||||
|
||||
SET "NODE_EXE=%~dp0\node.exe"
|
||||
IF NOT EXIST "%NODE_EXE%" (
|
||||
SET "NODE_EXE=node"
|
||||
)
|
||||
|
||||
SET "NPX_CLI_JS=%~dp0\node_modules\npm\bin\npx-cli.js"
|
||||
FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPX_CLI_JS%" prefix -g') DO (
|
||||
SET "NPM_PREFIX_NPX_CLI_JS=%%F\node_modules\npm\bin\npx-cli.js"
|
||||
)
|
||||
IF EXIST "%NPM_PREFIX_NPX_CLI_JS%" (
|
||||
SET "NPX_CLI_JS=%NPM_PREFIX_NPX_CLI_JS%"
|
||||
)
|
||||
|
||||
"%NODE_EXE%" "%NPX_CLI_JS%" %*
|
||||
4
deps/npm/doc/cli/npm-config.md
vendored
4
deps/npm/doc/cli/npm-config.md
vendored
@ -6,7 +6,7 @@ npm-config(1) -- Manage the npm configuration files
|
||||
npm config set <key> <value> [-g|--global]
|
||||
npm config get <key>
|
||||
npm config delete <key>
|
||||
npm config list
|
||||
npm config list [-l]
|
||||
npm config edit
|
||||
npm get <key>
|
||||
npm set <key> <value> [-g|--global]
|
||||
@ -48,7 +48,7 @@ Echo the config value to stdout.
|
||||
|
||||
npm config list
|
||||
|
||||
Show all the config settings.
|
||||
Show all the config settings. Use `-l` to also show defaults.
|
||||
|
||||
### delete
|
||||
|
||||
|
||||
3
deps/npm/doc/cli/npm-install.md
vendored
3
deps/npm/doc/cli/npm-install.md
vendored
@ -343,6 +343,9 @@ being installed.
|
||||
The `--no-shrinkwrap` argument, which will ignore an available
|
||||
package lock or shrinkwrap file and use the package.json instead.
|
||||
|
||||
The `--no-package-lock` argument will prevent npm from creating a
|
||||
`package-lock.json` file.
|
||||
|
||||
The `--nodedir=/path/to/node/source` argument will allow npm to find the
|
||||
node source code so that npm can compile native modules.
|
||||
|
||||
|
||||
7
deps/npm/doc/cli/npm-ls.md
vendored
7
deps/npm/doc/cli/npm-ls.md
vendored
@ -91,6 +91,13 @@ When "dev" or "development", is an alias to `dev`.
|
||||
|
||||
When "prod" or "production", is an alias to `production`.
|
||||
|
||||
### link
|
||||
|
||||
* Type: Boolean
|
||||
* Default: false
|
||||
|
||||
Display only dependencies which are linked
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
* npm-config(1)
|
||||
|
||||
4
deps/npm/doc/cli/npm-run-script.md
vendored
4
deps/npm/doc/cli/npm-run-script.md
vendored
@ -3,7 +3,7 @@ npm-run-script(1) -- Run arbitrary package scripts
|
||||
|
||||
## SYNOPSIS
|
||||
|
||||
npm run-script <command> [-- <args>...]
|
||||
npm run-script <command> [--silent] [-- <args>...]
|
||||
|
||||
alias: npm run
|
||||
|
||||
@ -50,6 +50,8 @@ not found in the `PATH`.
|
||||
If you try to run a script without having a `node_modules` directory and it fails,
|
||||
you will be given a warning to run `npm install`, just in case you've forgotten.
|
||||
|
||||
You can use the `--silent` flag to prevent showing `npm ERR!` output on error.
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
* npm-scripts(7)
|
||||
|
||||
5
deps/npm/doc/cli/npm-uninstall.md
vendored
5
deps/npm/doc/cli/npm-uninstall.md
vendored
@ -3,7 +3,7 @@ npm-uninstall(1) -- Remove a package
|
||||
|
||||
## SYNOPSIS
|
||||
|
||||
npm uninstall [<@scope>/]<pkg>[@<version>]... [-S|--save|-D|--save-dev|-O|--save-optional]
|
||||
npm uninstall [<@scope>/]<pkg>[@<version>]... [-S|--save|-D|--save-dev|-O|--save-optional|--no-save]
|
||||
|
||||
aliases: remove, rm, r, un, unlink
|
||||
|
||||
@ -28,6 +28,8 @@ the package version in your main package.json:
|
||||
|
||||
* `-O, --save-optional`: Package will be removed from your `optionalDependencies`.
|
||||
|
||||
* `--no-save`: Package will not be removed from your `package.json` file.
|
||||
|
||||
Further, if you have an `npm-shrinkwrap.json` then it will be updated as
|
||||
well.
|
||||
|
||||
@ -39,6 +41,7 @@ Examples:
|
||||
npm uninstall @myorg/privatepackage --save
|
||||
npm uninstall node-tap --save-dev
|
||||
npm uninstall dtrace-provider --save-optional
|
||||
npm uninstall lodash --no-save
|
||||
|
||||
## SEE ALSO
|
||||
|
||||
|
||||
7
deps/npm/doc/files/npm-folders.md
vendored
7
deps/npm/doc/files/npm-folders.md
vendored
@ -20,10 +20,9 @@ This document will tell you what it puts where.
|
||||
### prefix Configuration
|
||||
|
||||
The `prefix` config defaults to the location where node is installed.
|
||||
On most systems, this is `/usr/local`. On windows, this is the exact
|
||||
location of the node.exe binary. On Unix systems, it's one level up,
|
||||
since node is typically installed at `{prefix}/bin/node` rather than
|
||||
`{prefix}/node.exe`.
|
||||
On most systems, this is `/usr/local`. On Windows, it's `%AppData%\npm`.
|
||||
On Unix systems, it's one level up, since node is typically installed at
|
||||
`{prefix}/bin/node` rather than `{prefix}/node.exe`.
|
||||
|
||||
When the `global` flag is set, npm installs things into this prefix.
|
||||
When it is not set, it uses the root of the current package, or the
|
||||
|
||||
4
deps/npm/doc/files/npm-shrinkwrap.json.md
vendored
4
deps/npm/doc/files/npm-shrinkwrap.json.md
vendored
@ -5,7 +5,7 @@ npm-shrinkwrap.json(5) -- A publishable lockfile
|
||||
|
||||
`npm-shrinkwrap.json` is a file created by npm-shrinkwrap(1). It is identical to
|
||||
`package-lock.json`, with one major caveat: Unlike `package-lock.json`,
|
||||
`npm-shrinwkrap.json` may be included when publishing a package.
|
||||
`npm-shrinkwrap.json` may be included when publishing a package.
|
||||
|
||||
The recommended use-case for `npm-shrinkwrap.json` is applications deployed
|
||||
through the publishing process on the registry: for example, daemons and
|
||||
@ -13,7 +13,7 @@ command-line tools intended as global installs or `devDependencies`. It's
|
||||
strongly discouraged for library authors to publish this file, since that would
|
||||
prevent end users from having control over transitive dependency updates.
|
||||
|
||||
Additionally, if both `package-lock.json` and `npm-shrinwkrap.json` are present
|
||||
Additionally, if both `package-lock.json` and `npm-shrinkwrap.json` are present
|
||||
in a package root, `package-lock.json` will be ignored in favor of this file.
|
||||
|
||||
For full details and description of the `npm-shrinkwrap.json` file format, refer
|
||||
|
||||
2
deps/npm/doc/files/package-lock.json.md
vendored
2
deps/npm/doc/files/package-lock.json.md
vendored
@ -127,6 +127,6 @@ The dependencies of this dependency, exactly as at the top level.
|
||||
## SEE ALSO
|
||||
|
||||
* npm-shrinkwrap(1)
|
||||
* package-lock.json(5)
|
||||
* npm-shrinkwrap.json(5)
|
||||
* package.json(5)
|
||||
* npm-install(1)
|
||||
|
||||
39
deps/npm/doc/files/package.json.md
vendored
39
deps/npm/doc/files/package.json.md
vendored
@ -451,18 +451,28 @@ install time.
|
||||
|
||||
### Git URLs as Dependencies
|
||||
|
||||
Git urls can be of the form:
|
||||
Git urls are of the form:
|
||||
|
||||
git://github.com/user/project.git#commit-ish
|
||||
git+ssh://user@hostname:project.git#commit-ish
|
||||
git+ssh://user@hostname/project.git#commit-ish
|
||||
git+http://user@hostname/project/blah.git#commit-ish
|
||||
git+https://user@hostname/project/blah.git#commit-ish
|
||||
<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
|
||||
|
||||
The `commit-ish` can be any tag, sha, or branch which can be supplied as
|
||||
an argument to `git checkout`. The default is `master`.
|
||||
`<protocol>` is one of `git`, `git+ssh`, `git+http`, `git+https`, or
|
||||
`git+file`.
|
||||
|
||||
## GitHub URLs
|
||||
If `#<commit-ish>` is provided, it will be used to clone exactly that
|
||||
commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can
|
||||
be any valid semver range or exact version, and npm will look for any tags
|
||||
or refs matching that range in the remote repository, much as it would for a
|
||||
registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is
|
||||
specified, then `master` is used.
|
||||
|
||||
Examples:
|
||||
|
||||
git+ssh://git@github.com:npm/npm.git#v1.0.27
|
||||
git+ssh://git@github.com:npm/npm#semver:^5.0
|
||||
git+https://isaacs@github.com/npm/npm.git
|
||||
git://github.com/npm/npm.git#v1.0.27
|
||||
|
||||
### GitHub URLs
|
||||
|
||||
As of version 1.1.65, you can refer to GitHub urls as just "foo":
|
||||
"user/foo-project". Just as with git URLs, a `commit-ish` suffix can be
|
||||
@ -478,7 +488,7 @@ included. For example:
|
||||
}
|
||||
}
|
||||
|
||||
## Local Paths
|
||||
### Local Paths
|
||||
|
||||
As of version 2.0.0 you can provide a path to a local directory that contains a
|
||||
package. Local paths can be saved using `npm install -S` or
|
||||
@ -700,12 +710,11 @@ The host architecture is determined by `process.arch`
|
||||
|
||||
## preferGlobal
|
||||
|
||||
If your package is primarily a command-line application that should be
|
||||
installed globally, then set this value to `true` to provide a warning
|
||||
if it is installed locally.
|
||||
**DEPRECATED**
|
||||
|
||||
It doesn't actually prevent users from installing it locally, but it
|
||||
does help prevent some confusion if it doesn't work as expected.
|
||||
This option used to trigger an npm warning, but it will no longer warn. It is
|
||||
purely there for informational purposes. It is now recommended that you install
|
||||
any binaries as local devDependencies wherever possible.
|
||||
|
||||
## private
|
||||
|
||||
|
||||
23
deps/npm/doc/misc/npm-config.md
vendored
23
deps/npm/doc/misc/npm-config.md
vendored
@ -9,8 +9,14 @@ npm gets its configuration values from the following sources, sorted by priority
|
||||
|
||||
Putting `--foo bar` on the command line sets the `foo` configuration
|
||||
parameter to `"bar"`. A `--` argument tells the cli parser to stop
|
||||
reading flags. A `--flag` parameter that is at the *end* of the
|
||||
command will be given the value of `true`.
|
||||
reading flags. Using `--flag` without specifying any value will set
|
||||
the value to `true`.
|
||||
|
||||
Example: `--flag1 --flag2` will set both configuration parameters
|
||||
to `true`, while `--flag1 --flag2 bar` will set `flag1` to `true`,
|
||||
and `flag2` to `bar`. Finally, `--flag1 --flag2 -- bar` will set
|
||||
both configuration parameters to `true`, and the `bar` is taken
|
||||
as a command argument.
|
||||
|
||||
### Environment Variables
|
||||
|
||||
@ -21,7 +27,7 @@ configuration parameter to `bar`. Any environment configurations that
|
||||
are not given a value will be given the value of `true`. Config
|
||||
values are case-insensitive, so `NPM_CONFIG_FOO=bar` will work the
|
||||
same. However, please note that inside [npm-scripts](/misc/scripts)
|
||||
npm will set it's own environment variables and Node will prefer
|
||||
npm will set its own environment variables and Node will prefer
|
||||
those lowercase versions over any uppercase ones that you might set.
|
||||
For details see [this issue](https://github.com/npm/npm/issues/14528).
|
||||
|
||||
@ -31,9 +37,9 @@ The four relevant files are:
|
||||
|
||||
* per-project configuration file (`/path/to/my/project/.npmrc`)
|
||||
* per-user configuration file (defaults to `$HOME/.npmrc`; configurable via CLI
|
||||
option `--userconfig` or environment variable `$NPM_CONF_USERCONFIG`)
|
||||
option `--userconfig` or environment variable `$NPM_CONFIG_USERCONFIG`)
|
||||
* global configuration file (defaults to `$PREFIX/etc/npmrc`; configurable via
|
||||
CLI option `--globalconfig` or environment variable `$NPM_CONF_GLOBALCONFIG`)
|
||||
CLI option `--globalconfig` or environment variable `$NPM_CONFIG_GLOBALCONFIG`)
|
||||
* npm's built-in configuration file (`/path/to/npm/npmrc`)
|
||||
|
||||
See npmrc(5) for more details.
|
||||
@ -883,6 +889,13 @@ in to a private registry for the first time:
|
||||
will cause `@organization` to be mapped to the registry for future installation
|
||||
of packages specified according to the pattern `@organization/package`.
|
||||
|
||||
### script-shell
|
||||
|
||||
* Default: `null`
|
||||
* Type: path
|
||||
|
||||
The shell to use for scripts run with the `npm run` command.
|
||||
|
||||
### scripts-prepend-node-path
|
||||
|
||||
* Default: "warn-only"
|
||||
|
||||
5
deps/npm/doc/misc/npm-scripts.md
vendored
5
deps/npm/doc/misc/npm-scripts.md
vendored
@ -70,11 +70,6 @@ allow users to avoid the confusing behavior of existing npm versions and only
|
||||
run on `npm publish` (for instance, running the tests one last time to ensure
|
||||
they're in good shape).
|
||||
|
||||
**IMPORTANT:** As of `npm@5`, `prepublish` will _only_ be run for `npm
|
||||
publish`. This will make its behavior identical to `prepublishOnly`, so
|
||||
`npm@6` or later may drop support for the use of `prepublishOnly`, and then
|
||||
maybe we can all forget this embarrassing thing ever happened.
|
||||
|
||||
See <https://github.com/npm/npm/issues/10074> for a much lengthier
|
||||
justification, with further reading, for this change.
|
||||
|
||||
|
||||
276
deps/npm/doc/spec/package-lock.md
vendored
Normal file
276
deps/npm/doc/spec/package-lock.md
vendored
Normal file
@ -0,0 +1,276 @@
|
||||
# package-lock and npm-shrinkwrap
|
||||
|
||||
`npm` can have one of two different lock files:
|
||||
|
||||
* `package-lock.json`, which is ordinarily always present and is never published.
|
||||
* `npm-shrinkwrap.json`, which is created with `npm shrinkwrap` and usually published.
|
||||
|
||||
You can only have one of them and in the event that you have both,
|
||||
`npm-shrinkwrap.json` takes precedence. The files are exactly the same
|
||||
format and in fact all the `npm shrinkwrap` command does is rename your
|
||||
`package-lock.json`.
|
||||
|
||||
Through the rest of this document we will refer to the package-lock and
|
||||
`package-lock.json` but everything also applies to `npm-shrinkwrap.json`.
|
||||
|
||||
## File Format
|
||||
|
||||
### name
|
||||
|
||||
The name of the package this is a package-lock for. This must match what's in `package.json`.
|
||||
|
||||
### version
|
||||
|
||||
The version of the package this is a package-lock for. This must match what's in `package.json`.
|
||||
|
||||
### lockfileVersion *(new)*
|
||||
|
||||
An integer version, starting at `1` with the version number of this document
|
||||
whose semantics were used when generating this `package-lock.json`.
|
||||
|
||||
### preserveSymlinks *(new)*
|
||||
|
||||
Indicates that the install was done with the environment variable
|
||||
`NODE_PRESERVE_SYMLINKS` enabled. The installer should insist that the value of this
|
||||
property match that environment variable.
|
||||
|
||||
### dependencies
|
||||
|
||||
These are the modules installed in the `node_modules`. Some of these are
|
||||
dependencies some of these are transitive dependencies (that is,
|
||||
dependencies of our dependencies).
|
||||
|
||||
This is a mapping of package name to dependency object. Dependency objects have the
|
||||
following properties:
|
||||
|
||||
#### version *(changed)*
|
||||
|
||||
This is a specifier that uniquely identifies this package and should be
|
||||
usable in fetching a new copy of it.
|
||||
|
||||
* bundled dependencies: Regardless of source, this is a version number that is purely for informational purposes.
|
||||
* registry sources: This is a version number. (eg, `1.2.3`)
|
||||
* git sources: This is a git specifier with resolved committish. (eg, `git+https://example.com/foo/bar#115311855adb0789a0466714ed48a1499ffea97e`)
|
||||
* http tarball sources: This is the URL of the tarball. (eg, `https://example.com/example-1.3.0.tgz`)
|
||||
* local tarball sources: This is the file URL of the tarball. (eg `file:///opt/storage/example-1.3.0.tgz`)
|
||||
* local link sources: This is the file URL of the link. (eg `file:libs/our-module`)
|
||||
|
||||
#### integrity *(new)*
|
||||
|
||||
This is a [Standard Subresource
|
||||
Integrity](https://w3c.github.io/webappsec/specs/subresourceintegrity/) for
|
||||
this resource.
|
||||
|
||||
* For bundled dependencies this is not included, regardless of source.
|
||||
* For registry sources, this is the `integrity` that the registry provided, or if one wasn't provided the SHA1 in `shasum`.
|
||||
* For git sources this is the specific commit hash we cloned from.
|
||||
* For remote tarball sources this is an integrity based on a SHA512 of
|
||||
the file.
|
||||
* For local tarball sources: This is an integrity field based on the SHA512 of the file.
|
||||
|
||||
#### resolved
|
||||
|
||||
* For bundled dependencies this is not included, regardless of source.
|
||||
* For registry sources this is path of the tarball relative to the registry
|
||||
URL. If the tarball URL isn't on the same server as the registry URL then
|
||||
this is a complete URL.
|
||||
|
||||
#### link *(new)*
|
||||
|
||||
If this module was symlinked in development but had semver in the
|
||||
`package.json` then this is the relative path of that link.
|
||||
|
||||
Discussion of the semantics of this will go in the symlinks RFC.
|
||||
|
||||
Implementation note: To be implemented post npm@5.
|
||||
|
||||
#### bundled *(new)*
|
||||
|
||||
If true, this is the bundled dependency and will be installed by the parent
|
||||
module. When installing, this module will be extracted from the parent
|
||||
module during the extract phase, not installed as a separate dependency.
|
||||
|
||||
#### dev
|
||||
|
||||
If true then this dependency is either a development dependency ONLY of the
|
||||
top level module or a transitive dependency of one. This is false for
|
||||
dependencies that are both a development dependency of the top level and a
|
||||
transitive dependency of a non-development dependency of the top level.
|
||||
|
||||
#### optional
|
||||
|
||||
If true then this dependency is either an optional dependency ONLY of the
|
||||
top level module or a transitive dependency of one. This is false for
|
||||
dependencies that are both an optional dependency of the top level and a
|
||||
transitive dependency of a non-optional dependency of the top level.
|
||||
|
||||
All optional dependencies should be included even if they're uninstallable
|
||||
on the current platform.
|
||||
|
||||
#### from *(deprecated)*
|
||||
|
||||
This is a record of what specifier was used to originally install this
|
||||
package. This should not be included in new `package-lock.json` files.
|
||||
|
||||
#### requires
|
||||
|
||||
This is a mapping of module name to version. This is a list of everything
|
||||
this module requires, regardless of where it will be installed. The version
|
||||
should match via normal matching rules a dependency either in our
|
||||
`dependencies` or in a level higher than us.
|
||||
|
||||
#### dependencies
|
||||
|
||||
Exactly like `dependencies` at the top level, this is a list of modules to
|
||||
install in the `node_modules` of this module.
|
||||
|
||||
## Generating
|
||||
|
||||
### `npm init`
|
||||
|
||||
If neither a `package-lock.json` nor an `npm-shrinkwrap.json` exist then
|
||||
`npm init` will create a `package-lock.json`. This is functionally
|
||||
equivalent to running `npm shrinkwrap` after the current init completes and
|
||||
renaming the result to `package-lock.json`.
|
||||
|
||||
### `npm install --save`
|
||||
|
||||
If either an `npm-shrinkwrap.json` or a `package-lock.json` exists then it
|
||||
will be updated.
|
||||
|
||||
If neither exist then a `package-lock.json` should be generated.
|
||||
|
||||
If a `package.json` does not exist, it should be generated. The generated
|
||||
`package.json` should be empty, as in:
|
||||
|
||||
```
|
||||
{
|
||||
"dependencies": {
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
If the user wants to get a default package name/version added they can run `npm init`.
|
||||
|
||||
### `npm shrinkwrap`
|
||||
|
||||
If a `package-lock.json` exists, rename it to `npm-shrinkwrap.json`.
|
||||
Refresh the data from the installer's ideal tree.
|
||||
|
||||
The top level `name` and `version` come from the `package.json`. It is an
|
||||
error if either are missing or invalid.
|
||||
|
||||
#### dependencies.dev
|
||||
|
||||
This is `true` if this dependency is ONLY installed to fulfill either a top
|
||||
level development dependency, or one of its transitive dependencies.
|
||||
|
||||
Given:
|
||||
```
|
||||
B (Dev) → C
|
||||
```
|
||||
|
||||
Then both B and C would be `dev: true`.
|
||||
|
||||
Given:
|
||||
```
|
||||
A → B → C
|
||||
B (Dev) -> C
|
||||
```
|
||||
|
||||
Then all dependencies would be `dev: false`.
|
||||
|
||||
#### dependencies.optional
|
||||
|
||||
This is `true` if this dependency is ONLY ever either an optional dependency
|
||||
or a transitive dependency of optional dependencies.
|
||||
|
||||
Given:
|
||||
```
|
||||
A (Opt) → B → C
|
||||
```
|
||||
|
||||
Then all three of A, B and C would be flagged as optional.
|
||||
|
||||
Given:
|
||||
```
|
||||
A (Opt) → B → C
|
||||
D → C
|
||||
```
|
||||
|
||||
Then A and B would be flagged as optional, but C would not be.
|
||||
|
||||
Given:
|
||||
```
|
||||
A (Opt) → B → C
|
||||
D → A
|
||||
```
|
||||
|
||||
Then none would be flagged as optional.
|
||||
|
||||
## Installing
|
||||
|
||||
If the `packageIntegrity` in the `package-lock.json` differs from the one
|
||||
computed from the `package.json` then places where the `package.json` is
|
||||
incompatible with the `package-lock.json` a new module should be installed.
|
||||
That is, while the `package-lock.json` ordinarily defines the state of your
|
||||
project, if your `package.json` is edited independently it will take
|
||||
precedence.
|
||||
|
||||
The `package-lock.json` describes the exact tree that `npm` should create.
|
||||
Any deviation between the `package.json` and the shrinkwrap/lock should
|
||||
result in a warning be issued. This includes:
|
||||
|
||||
* Modules in `package.json` but missing from the `package-lock.json`
|
||||
* Modules in the `package-lock.json` but missing from the `package.json`.
|
||||
* Modules in `package.json` whose specifiers don't match the version in `package-lock.json`.
|
||||
|
||||
Warn if the `lockfileVersion` in the `package-lock.json` is for a different
|
||||
major version than we implement.
|
||||
|
||||
Module resolution from package-lock data works as such:
|
||||
|
||||
* If install was run with `--resolve-links` and a dependency has a `link`
|
||||
property then a symlink is made using that. If the version of the
|
||||
destination can not be matched to the package-lock and/or the package.json
|
||||
then a warning will be issued.
|
||||
|
||||
* Otherwise, if a `integrity` is available then we try to install it from the cache using it.
|
||||
|
||||
If `integrity` is unavailable or we are unable to locate a module from the `integrity` then:
|
||||
|
||||
* If `lockfileVersion` is set:
|
||||
* Install using the value of `version` and validate the result against the
|
||||
`integrity`.
|
||||
* Otherwise, try these in turn and validate the result against the `integrity`:
|
||||
* `resolved`, then `from`, then `version.
|
||||
* `from` can be either `package@specifier` or just `specifier`.
|
||||
|
||||
Regardless of how the module is installed the metadata in the installed
|
||||
module should be identical to what it would have been if the module were
|
||||
installed w/o a package-lock.
|
||||
|
||||
## Implied Changes To Other Commands
|
||||
|
||||
### `npm rm --save`
|
||||
|
||||
Currently if you ask to remove a package that's both a direct and a
|
||||
transitive dependency, we'll remove the package from `node_modules` even if
|
||||
this results in a broken tree. This was chosen at the time because we felt
|
||||
that users would expect `npm rm pkgname` to be equivalent of
|
||||
`rm -rf node_modules/pkgname`.
|
||||
|
||||
As you are no longer going to be allowed to put your `node_modules` in a
|
||||
state that's not a valid package-lock, this means this behavior is no longer
|
||||
valid. Instead we should follow normal rules, removing it from the
|
||||
dependencies for the top level but only removing the module on disk if
|
||||
nothing requires it any more.
|
||||
|
||||
## Additional fields / Adding new fields
|
||||
|
||||
Installers should ignore any field they aren't aware of. It's not an error
|
||||
to have additional properities in the package-lock or lock file.
|
||||
|
||||
Installers that want to add new fields should either have one added via RFC
|
||||
in the npm issue tracker and an accompanying documentation PR, or should prefix
|
||||
it with the name of their project.
|
||||
7
deps/npm/html/doc/README.html
vendored
7
deps/npm/html/doc/README.html
vendored
@ -106,8 +106,9 @@ you should <a href="https://docs.npmjs.com/misc/developers">read this</a></p>
|
||||
</ul>
|
||||
<p>Be sure to include <em>all</em> of the output from the npm command that didn't work
|
||||
as expected. The <code>npm-debug.log</code> file is also helpful to provide.</p>
|
||||
<p>You can also look for isaacs in #node.js on irc://irc.freenode.net. She
|
||||
will no doubt tell you to put the output in a gist or email.</p>
|
||||
<p>You can also find npm people in <code>#npm</code> on <a href="https://package.community/">https://package.community/</a> or
|
||||
<a href="https://twitter.com/npm_support">on Twitter</a>. Whoever responds will no
|
||||
doubt tell you to put the output in a gist or email.</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="cli/npm.html">npm(1)</a></li>
|
||||
@ -126,5 +127,5 @@ will no doubt tell you to put the output in a gist or email.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer"><a href="../doc/README.html">README</a> — npm@5.0.3</p>
|
||||
<p id="footer"><a href="../doc/README.html">README</a> — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-access.html
vendored
2
deps/npm/html/doc/cli/npm-access.html
vendored
@ -84,5 +84,5 @@ with an HTTP 402 status code (logically enough), unless you use
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-access — npm@5.0.3</p>
|
||||
<p id="footer">npm-access — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-adduser.html
vendored
2
deps/npm/html/doc/cli/npm-adduser.html
vendored
@ -81,5 +81,5 @@ username/password entry in legacy npm.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-adduser — npm@5.0.3</p>
|
||||
<p id="footer">npm-adduser — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-bin.html
vendored
2
deps/npm/html/doc/cli/npm-bin.html
vendored
@ -35,5 +35,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-bin — npm@5.0.3</p>
|
||||
<p id="footer">npm-bin — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-bugs.html
vendored
2
deps/npm/html/doc/cli/npm-bugs.html
vendored
@ -55,5 +55,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-bugs — npm@5.0.3</p>
|
||||
<p id="footer">npm-bugs — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-build.html
vendored
2
deps/npm/html/doc/cli/npm-build.html
vendored
@ -40,5 +40,5 @@ directly, run:</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-build — npm@5.0.3</p>
|
||||
<p id="footer">npm-build — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-bundle.html
vendored
2
deps/npm/html/doc/cli/npm-bundle.html
vendored
@ -31,5 +31,5 @@ install packages into the local space.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-bundle — npm@5.0.3</p>
|
||||
<p id="footer">npm-bundle — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-cache.html
vendored
2
deps/npm/html/doc/cli/npm-cache.html
vendored
@ -89,5 +89,5 @@ verify</code>.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-cache — npm@5.0.3</p>
|
||||
<p id="footer">npm-cache — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-completion.html
vendored
2
deps/npm/html/doc/cli/npm-completion.html
vendored
@ -43,5 +43,5 @@ completions based on the arguments.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-completion — npm@5.0.3</p>
|
||||
<p id="footer">npm-completion — npm@5.3.0</p>
|
||||
|
||||
|
||||
6
deps/npm/html/doc/cli/npm-config.html
vendored
6
deps/npm/html/doc/cli/npm-config.html
vendored
@ -14,7 +14,7 @@
|
||||
<pre><code>npm config set <key> <value> [-g|--global]
|
||||
npm config get <key>
|
||||
npm config delete <key>
|
||||
npm config list
|
||||
npm config list [-l]
|
||||
npm config edit
|
||||
npm get <key>
|
||||
npm set <key> <value> [-g|--global]
|
||||
@ -39,7 +39,7 @@ of the user and global npmrc files.</p>
|
||||
</code></pre><p>Echo the config value to stdout.</p>
|
||||
<h3 id="list">list</h3>
|
||||
<pre><code>npm config list
|
||||
</code></pre><p>Show all the config settings.</p>
|
||||
</code></pre><p>Show all the config settings. Use <code>-l</code> to also show defaults.</p>
|
||||
<h3 id="delete">delete</h3>
|
||||
<pre><code>npm config delete key
|
||||
</code></pre><p>Deletes the key from all configuration files.</p>
|
||||
@ -67,5 +67,5 @@ global config.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-config — npm@5.0.3</p>
|
||||
<p id="footer">npm-config — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-dedupe.html
vendored
2
deps/npm/html/doc/cli/npm-dedupe.html
vendored
@ -61,5 +61,5 @@ result in new modules being installed.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-dedupe — npm@5.0.3</p>
|
||||
<p id="footer">npm-dedupe — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-deprecate.html
vendored
2
deps/npm/html/doc/cli/npm-deprecate.html
vendored
@ -38,5 +38,5 @@ something like this:</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-deprecate — npm@5.0.3</p>
|
||||
<p id="footer">npm-deprecate — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-dist-tag.html
vendored
2
deps/npm/html/doc/cli/npm-dist-tag.html
vendored
@ -86,5 +86,5 @@ begin with a number or the letter <code>v</code>.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-dist-tag — npm@5.0.3</p>
|
||||
<p id="footer">npm-dist-tag — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-docs.html
vendored
2
deps/npm/html/doc/cli/npm-docs.html
vendored
@ -56,5 +56,5 @@ the current folder and use the <code>name</code> property.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-docs — npm@5.0.3</p>
|
||||
<p id="footer">npm-docs — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-doctor.html
vendored
2
deps/npm/html/doc/cli/npm-doctor.html
vendored
@ -103,4 +103,4 @@ cache, you should probably run <code>npm cache clean</code> and reset the cache.
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-doctor — npm@5.0.3</p>
|
||||
<p id="footer">npm-doctor — npm@5.3.0</p>
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-edit.html
vendored
2
deps/npm/html/doc/cli/npm-edit.html
vendored
@ -49,5 +49,5 @@ or <code>"notepad"</code> on Windows.</li>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-edit — npm@5.0.3</p>
|
||||
<p id="footer">npm-edit — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-explore.html
vendored
2
deps/npm/html/doc/cli/npm-explore.html
vendored
@ -49,5 +49,5 @@ Windows</li>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-explore — npm@5.0.3</p>
|
||||
<p id="footer">npm-explore — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-help-search.html
vendored
2
deps/npm/html/doc/cli/npm-help-search.html
vendored
@ -45,5 +45,5 @@ where the terms were found in the documentation.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-help-search — npm@5.0.3</p>
|
||||
<p id="footer">npm-help-search — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-help.html
vendored
2
deps/npm/html/doc/cli/npm-help.html
vendored
@ -50,5 +50,5 @@ matches are equivalent to specifying a topic name.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-help — npm@5.0.3</p>
|
||||
<p id="footer">npm-help — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-init.html
vendored
2
deps/npm/html/doc/cli/npm-init.html
vendored
@ -48,5 +48,5 @@ defaults and not prompt you for any options.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-init — npm@5.0.3</p>
|
||||
<p id="footer">npm-init — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-install-test.html
vendored
2
deps/npm/html/doc/cli/npm-install-test.html
vendored
@ -42,5 +42,5 @@ takes exactly the same arguments as <code>npm install</code>.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-install-test — npm@5.0.3</p>
|
||||
<p id="footer">npm-install-test — npm@5.3.0</p>
|
||||
|
||||
|
||||
4
deps/npm/html/doc/cli/npm-install.html
vendored
4
deps/npm/html/doc/cli/npm-install.html
vendored
@ -278,6 +278,8 @@ any binaries the package might contain.</p>
|
||||
being installed.</p>
|
||||
<p>The <code>--no-shrinkwrap</code> argument, which will ignore an available
|
||||
package lock or shrinkwrap file and use the package.json instead.</p>
|
||||
<p>The <code>--no-package-lock</code> argument will prevent npm from creating a
|
||||
<code>package-lock.json</code> file.</p>
|
||||
<p>The <code>--nodedir=/path/to/node/source</code> argument will allow npm to find the
|
||||
node source code so that npm can compile native modules.</p>
|
||||
<p>The <code>--only={prod[uction]|dev[elopment]}</code> argument will cause either only
|
||||
@ -365,5 +367,5 @@ affects a real use-case, it will be investigated.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-install — npm@5.0.3</p>
|
||||
<p id="footer">npm-install — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-link.html
vendored
2
deps/npm/html/doc/cli/npm-link.html
vendored
@ -74,5 +74,5 @@ include that scope, e.g.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-link — npm@5.0.3</p>
|
||||
<p id="footer">npm-link — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-logout.html
vendored
2
deps/npm/html/doc/cli/npm-logout.html
vendored
@ -51,5 +51,5 @@ it takes precedence.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-logout — npm@5.0.3</p>
|
||||
<p id="footer">npm-logout — npm@5.3.0</p>
|
||||
|
||||
|
||||
10
deps/npm/html/doc/cli/npm-ls.html
vendored
10
deps/npm/html/doc/cli/npm-ls.html
vendored
@ -21,7 +21,7 @@ installed, as well as their dependencies, in a tree-structure.</p>
|
||||
limit the results to only the paths to the packages named. Note that
|
||||
nested packages will <em>also</em> show the paths to the specified packages.
|
||||
For example, running <code>npm ls promzard</code> in npm's source tree will show:</p>
|
||||
<pre><code>npm@5.0.3 /path/to/npm
|
||||
<pre><code>npm@5.3.0 /path/to/npm
|
||||
└─┬ init-package-json@0.0.4
|
||||
└── promzard@0.1.5
|
||||
</code></pre><p>It will print out extraneous, missing, and invalid packages.</p>
|
||||
@ -80,6 +80,12 @@ project.</p>
|
||||
</ul>
|
||||
<p>When "dev" or "development", is an alias to <code>dev</code>.</p>
|
||||
<p>When "prod" or "production", is an alias to <code>production</code>.</p>
|
||||
<h3 id="link">link</h3>
|
||||
<ul>
|
||||
<li>Type: Boolean</li>
|
||||
<li>Default: false</li>
|
||||
</ul>
|
||||
<p>Display only dependencies which are linked</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../cli/npm-config.html">npm-config(1)</a></li>
|
||||
@ -104,5 +110,5 @@ project.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-ls — npm@5.0.3</p>
|
||||
<p id="footer">npm-ls — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-outdated.html
vendored
2
deps/npm/html/doc/cli/npm-outdated.html
vendored
@ -116,5 +116,5 @@ project.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-outdated — npm@5.0.3</p>
|
||||
<p id="footer">npm-outdated — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-owner.html
vendored
2
deps/npm/html/doc/cli/npm-owner.html
vendored
@ -51,5 +51,5 @@ that is not implemented at this time.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-owner — npm@5.0.3</p>
|
||||
<p id="footer">npm-owner — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-pack.html
vendored
2
deps/npm/html/doc/cli/npm-pack.html
vendored
@ -41,5 +41,5 @@ overwritten the second time.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-pack — npm@5.0.3</p>
|
||||
<p id="footer">npm-pack — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-ping.html
vendored
2
deps/npm/html/doc/cli/npm-ping.html
vendored
@ -32,5 +32,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-ping — npm@5.0.3</p>
|
||||
<p id="footer">npm-ping — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-prefix.html
vendored
2
deps/npm/html/doc/cli/npm-prefix.html
vendored
@ -38,5 +38,5 @@ to contain a package.json file unless <code>-g</code> is also specified.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-prefix — npm@5.0.3</p>
|
||||
<p id="footer">npm-prefix — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-prune.html
vendored
2
deps/npm/html/doc/cli/npm-prune.html
vendored
@ -40,5 +40,5 @@ negate <code>NODE_ENV</code> being set to <code>production</code>.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-prune — npm@5.0.3</p>
|
||||
<p id="footer">npm-prune — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-publish.html
vendored
2
deps/npm/html/doc/cli/npm-publish.html
vendored
@ -79,5 +79,5 @@ packs them into a tarball to be uploaded to the registry.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-publish — npm@5.0.3</p>
|
||||
<p id="footer">npm-publish — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-rebuild.html
vendored
2
deps/npm/html/doc/cli/npm-rebuild.html
vendored
@ -35,5 +35,5 @@ the new binary.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-rebuild — npm@5.0.3</p>
|
||||
<p id="footer">npm-rebuild — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-repo.html
vendored
2
deps/npm/html/doc/cli/npm-repo.html
vendored
@ -41,5 +41,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-repo — npm@5.0.3</p>
|
||||
<p id="footer">npm-repo — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-restart.html
vendored
2
deps/npm/html/doc/cli/npm-restart.html
vendored
@ -53,5 +53,5 @@ behavior will be accompanied by an increase in major version number</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-restart — npm@5.0.3</p>
|
||||
<p id="footer">npm-restart — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-root.html
vendored
2
deps/npm/html/doc/cli/npm-root.html
vendored
@ -35,5 +35,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-root — npm@5.0.3</p>
|
||||
<p id="footer">npm-root — npm@5.3.0</p>
|
||||
|
||||
|
||||
5
deps/npm/html/doc/cli/npm-run-script.html
vendored
5
deps/npm/html/doc/cli/npm-run-script.html
vendored
@ -11,7 +11,7 @@
|
||||
|
||||
<h1><a href="../cli/npm-run-script.html">npm-run-script</a></h1> <p>Run arbitrary package scripts</p>
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm run-script <command> [-- <args>...]
|
||||
<pre><code>npm run-script <command> [--silent] [-- <args>...]
|
||||
|
||||
alias: npm run
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
@ -46,6 +46,7 @@ default in <code>npm</code> v3), this is only performed when that <code>node</co
|
||||
not found in the <code>PATH</code>.</p>
|
||||
<p>If you try to run a script without having a <code>node_modules</code> directory and it fails,
|
||||
you will be given a warning to run <code>npm install</code>, just in case you've forgotten.</p>
|
||||
<p>You can use the <code>--silent</code> flag to prevent showing <code>npm ERR!</code> output on error.</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li>
|
||||
@ -66,5 +67,5 @@ you will be given a warning to run <code>npm install</code>, just in case you
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-run-script — npm@5.0.3</p>
|
||||
<p id="footer">npm-run-script — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-search.html
vendored
2
deps/npm/html/doc/cli/npm-search.html
vendored
@ -109,5 +109,5 @@ setting.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-search — npm@5.0.3</p>
|
||||
<p id="footer">npm-search — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-shrinkwrap.html
vendored
2
deps/npm/html/doc/cli/npm-shrinkwrap.html
vendored
@ -41,5 +41,5 @@ of package locks in npm, see <a href="../files/npm-package-locks.html">npm-packa
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-shrinkwrap — npm@5.0.3</p>
|
||||
<p id="footer">npm-shrinkwrap — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-star.html
vendored
2
deps/npm/html/doc/cli/npm-star.html
vendored
@ -36,5 +36,5 @@ a vaguely positive way to show that you care.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-star — npm@5.0.3</p>
|
||||
<p id="footer">npm-star — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-stars.html
vendored
2
deps/npm/html/doc/cli/npm-stars.html
vendored
@ -36,5 +36,5 @@ you will most certainly enjoy this command.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-stars — npm@5.0.3</p>
|
||||
<p id="footer">npm-stars — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-start.html
vendored
2
deps/npm/html/doc/cli/npm-start.html
vendored
@ -39,5 +39,5 @@ more details.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-start — npm@5.0.3</p>
|
||||
<p id="footer">npm-start — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-stop.html
vendored
2
deps/npm/html/doc/cli/npm-stop.html
vendored
@ -34,5 +34,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-stop — npm@5.0.3</p>
|
||||
<p id="footer">npm-stop — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-team.html
vendored
2
deps/npm/html/doc/cli/npm-team.html
vendored
@ -67,5 +67,5 @@ use the <code>npm access</code> command to grant or revoke the appropriate permi
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-team — npm@5.0.3</p>
|
||||
<p id="footer">npm-team — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-test.html
vendored
2
deps/npm/html/doc/cli/npm-test.html
vendored
@ -36,5 +36,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-test — npm@5.0.3</p>
|
||||
<p id="footer">npm-test — npm@5.3.0</p>
|
||||
|
||||
|
||||
7
deps/npm/html/doc/cli/npm-uninstall.html
vendored
7
deps/npm/html/doc/cli/npm-uninstall.html
vendored
@ -11,7 +11,7 @@
|
||||
|
||||
<h1><a href="../cli/npm-uninstall.html">npm-uninstall</a></h1> <p>Remove a package</p>
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm uninstall [<@scope>/]<pkg>[@<version>]... [-S|--save|-D|--save-dev|-O|--save-optional]
|
||||
<pre><code>npm uninstall [<@scope>/]<pkg>[@<version>]... [-S|--save|-D|--save-dev|-O|--save-optional|--no-save]
|
||||
|
||||
aliases: remove, rm, r, un, unlink
|
||||
</code></pre><h2 id="description">DESCRIPTION</h2>
|
||||
@ -30,6 +30,8 @@ the package version in your main package.json:</p>
|
||||
</li>
|
||||
<li><p><code>-O, --save-optional</code>: Package will be removed from your <code>optionalDependencies</code>.</p>
|
||||
</li>
|
||||
<li><p><code>--no-save</code>: Package will not be removed from your <code>package.json</code> file.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>Further, if you have an <code>npm-shrinkwrap.json</code> then it will be updated as
|
||||
well.</p>
|
||||
@ -39,6 +41,7 @@ well.</p>
|
||||
npm uninstall @myorg/privatepackage --save
|
||||
npm uninstall node-tap --save-dev
|
||||
npm uninstall dtrace-provider --save-optional
|
||||
npm uninstall lodash --no-save
|
||||
</code></pre><h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../cli/npm-prune.html">npm-prune(1)</a></li>
|
||||
@ -60,5 +63,5 @@ npm uninstall dtrace-provider --save-optional
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-uninstall — npm@5.0.3</p>
|
||||
<p id="footer">npm-uninstall — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-unpublish.html
vendored
2
deps/npm/html/doc/cli/npm-unpublish.html
vendored
@ -51,5 +51,5 @@ contact support@npmjs.com.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-unpublish — npm@5.0.3</p>
|
||||
<p id="footer">npm-unpublish — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-update.html
vendored
2
deps/npm/html/doc/cli/npm-update.html
vendored
@ -118,5 +118,5 @@ be <em>downgraded</em>.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-update — npm@5.0.3</p>
|
||||
<p id="footer">npm-update — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-version.html
vendored
2
deps/npm/html/doc/cli/npm-version.html
vendored
@ -114,5 +114,5 @@ to the same value as the current version.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-version — npm@5.0.3</p>
|
||||
<p id="footer">npm-version — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-view.html
vendored
2
deps/npm/html/doc/cli/npm-view.html
vendored
@ -86,5 +86,5 @@ the field name.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-view — npm@5.0.3</p>
|
||||
<p id="footer">npm-view — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/cli/npm-whoami.html
vendored
2
deps/npm/html/doc/cli/npm-whoami.html
vendored
@ -33,5 +33,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-whoami — npm@5.0.3</p>
|
||||
<p id="footer">npm-whoami — npm@5.3.0</p>
|
||||
|
||||
|
||||
6
deps/npm/html/doc/cli/npm.html
vendored
6
deps/npm/html/doc/cli/npm.html
vendored
@ -13,7 +13,7 @@
|
||||
<h2 id="synopsis">SYNOPSIS</h2>
|
||||
<pre><code>npm <command> [args]
|
||||
</code></pre><h2 id="version">VERSION</h2>
|
||||
<p>5.0.3</p>
|
||||
<p>5.3.0</p>
|
||||
<h2 id="description">DESCRIPTION</h2>
|
||||
<p>npm is the package manager for the Node JavaScript platform. It puts
|
||||
modules in place so that node can find them, and manages dependency
|
||||
@ -126,7 +126,7 @@ will no doubt tell you to put the output in a gist or email.</p>
|
||||
<p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> ::
|
||||
<a href="https://github.com/isaacs/">isaacs</a> ::
|
||||
<a href="http://twitter.com/izs">@izs</a> ::
|
||||
<a href="mailto:i@izs.me">i@izs.me</a></p>
|
||||
<a href="mailto:i@izs.me">i@izs.me</a></p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../cli/npm-help.html">npm-help(1)</a></li>
|
||||
@ -150,5 +150,5 @@ will no doubt tell you to put the output in a gist or email.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm — npm@5.0.3</p>
|
||||
<p id="footer">npm — npm@5.3.0</p>
|
||||
|
||||
|
||||
9
deps/npm/html/doc/files/npm-folders.html
vendored
9
deps/npm/html/doc/files/npm-folders.html
vendored
@ -25,10 +25,9 @@ is installed.</li>
|
||||
</ul>
|
||||
<h3 id="prefix-configuration">prefix Configuration</h3>
|
||||
<p>The <code>prefix</code> config defaults to the location where node is installed.
|
||||
On most systems, this is <code>/usr/local</code>. On windows, this is the exact
|
||||
location of the node.exe binary. On Unix systems, it's one level up,
|
||||
since node is typically installed at <code>{prefix}/bin/node</code> rather than
|
||||
<code>{prefix}/node.exe</code>.</p>
|
||||
On most systems, this is <code>/usr/local</code>. On Windows, it's <code>%AppData%\npm</code>.
|
||||
On Unix systems, it's one level up, since node is typically installed at
|
||||
<code>{prefix}/bin/node</code> rather than <code>{prefix}/node.exe</code>.</p>
|
||||
<p>When the <code>global</code> flag is set, npm installs things into this prefix.
|
||||
When it is not set, it uses the root of the current package, or the
|
||||
current working directory if not in a package already.</p>
|
||||
@ -182,5 +181,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-folders — npm@5.0.3</p>
|
||||
<p id="footer">npm-folders — npm@5.3.0</p>
|
||||
|
||||
|
||||
9
deps/npm/html/doc/files/npm-global.html
vendored
9
deps/npm/html/doc/files/npm-global.html
vendored
@ -25,10 +25,9 @@ is installed.</li>
|
||||
</ul>
|
||||
<h3 id="prefix-configuration">prefix Configuration</h3>
|
||||
<p>The <code>prefix</code> config defaults to the location where node is installed.
|
||||
On most systems, this is <code>/usr/local</code>. On windows, this is the exact
|
||||
location of the node.exe binary. On Unix systems, it's one level up,
|
||||
since node is typically installed at <code>{prefix}/bin/node</code> rather than
|
||||
<code>{prefix}/node.exe</code>.</p>
|
||||
On most systems, this is <code>/usr/local</code>. On Windows, it's <code>%AppData%\npm</code>.
|
||||
On Unix systems, it's one level up, since node is typically installed at
|
||||
<code>{prefix}/bin/node</code> rather than <code>{prefix}/node.exe</code>.</p>
|
||||
<p>When the <code>global</code> flag is set, npm installs things into this prefix.
|
||||
When it is not set, it uses the root of the current package, or the
|
||||
current working directory if not in a package already.</p>
|
||||
@ -182,5 +181,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-folders — npm@5.0.3</p>
|
||||
<p id="footer">npm-folders — npm@5.3.0</p>
|
||||
|
||||
|
||||
38
deps/npm/html/doc/files/npm-json.html
vendored
38
deps/npm/html/doc/files/npm-json.html
vendored
@ -342,15 +342,22 @@ tarball or git URL.</p>
|
||||
<p>This tarball will be downloaded and installed locally to your package at
|
||||
install time.</p>
|
||||
<h3 id="git-urls-as-dependencies">Git URLs as Dependencies</h3>
|
||||
<p>Git urls can be of the form:</p>
|
||||
<pre><code>git://github.com/user/project.git#commit-ish
|
||||
git+ssh://user@hostname:project.git#commit-ish
|
||||
git+ssh://user@hostname/project.git#commit-ish
|
||||
git+http://user@hostname/project/blah.git#commit-ish
|
||||
git+https://user@hostname/project/blah.git#commit-ish
|
||||
</code></pre><p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as
|
||||
an argument to <code>git checkout</code>. The default is <code>master</code>.</p>
|
||||
<h2 id="github-urls">GitHub URLs</h2>
|
||||
<p>Git urls are of the form:</p>
|
||||
<pre><code><protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
|
||||
</code></pre><p><code><protocol></code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, <code>git+https</code>, or
|
||||
<code>git+file</code>.</p>
|
||||
<p>If <code>#<commit-ish></code> is provided, it will be used to clone exactly that
|
||||
commit. If the commit-ish has the format <code>#semver:<semver></code>, <code><semver></code> can
|
||||
be any valid semver range or exact version, and npm will look for any tags
|
||||
or refs matching that range in the remote repository, much as it would for a
|
||||
registry dependency. If neither <code>#<commit-ish></code> or <code>#semver:<semver></code> is
|
||||
specified, then <code>master</code> is used.</p>
|
||||
<p>Examples:</p>
|
||||
<pre><code>git+ssh://git@github.com:npm/npm.git#v1.0.27
|
||||
git+ssh://git@github.com:npm/npm#semver:^5.0
|
||||
git+https://isaacs@github.com/npm/npm.git
|
||||
git://github.com/npm/npm.git#v1.0.27
|
||||
</code></pre><h3 id="github-urls">GitHub URLs</h3>
|
||||
<p>As of version 1.1.65, you can refer to GitHub urls as just "foo":
|
||||
"user/foo-project". Just as with git URLs, a <code>commit-ish</code> suffix can be
|
||||
included. For example:</p>
|
||||
@ -363,7 +370,7 @@ included. For example:</p>
|
||||
"module": "user/repo#feature\/branch"
|
||||
}
|
||||
}
|
||||
</code></pre><h2 id="local-paths">Local Paths</h2>
|
||||
</code></pre><h3 id="local-paths">Local Paths</h3>
|
||||
<p>As of version 2.0.0 you can provide a path to a local directory that contains a
|
||||
package. Local paths can be saved using <code>npm install -S</code> or
|
||||
<code>npm install --save</code>, using any of these forms:</p>
|
||||
@ -523,11 +530,10 @@ you can specify which ones.</p>
|
||||
<pre><code>"cpu" : [ "!arm", "!mips" ]
|
||||
</code></pre><p>The host architecture is determined by <code>process.arch</code></p>
|
||||
<h2 id="preferglobal">preferGlobal</h2>
|
||||
<p>If your package is primarily a command-line application that should be
|
||||
installed globally, then set this value to <code>true</code> to provide a warning
|
||||
if it is installed locally.</p>
|
||||
<p>It doesn't actually prevent users from installing it locally, but it
|
||||
does help prevent some confusion if it doesn't work as expected.</p>
|
||||
<p><strong>DEPRECATED</strong></p>
|
||||
<p>This option used to trigger an npm warning, but it will no longer warn. It is
|
||||
purely there for informational purposes. It is now recommended that you install
|
||||
any binaries as local devDependencies wherever possible.</p>
|
||||
<h2 id="private">private</h2>
|
||||
<p>If you set <code>"private": true</code> in your package.json, then npm will refuse
|
||||
to publish it.</p>
|
||||
@ -587,5 +593,5 @@ ignored.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">package.json — npm@5.0.3</p>
|
||||
<p id="footer">package.json — npm@5.3.0</p>
|
||||
|
||||
|
||||
@ -145,4 +145,4 @@ if any transitive dependencies were updated, hoisted, etc.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-package-locks — npm@5.0.3</p>
|
||||
<p id="footer">npm-package-locks — npm@5.3.0</p>
|
||||
|
||||
@ -13,13 +13,13 @@
|
||||
<h2 id="description">DESCRIPTION</h2>
|
||||
<p><code>npm-shrinkwrap.json</code> is a file created by <a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a>. It is identical to
|
||||
<code>package-lock.json</code>, with one major caveat: Unlike <code>package-lock.json</code>,
|
||||
<code>npm-shrinwkrap.json</code> may be included when publishing a package.</p>
|
||||
<code>npm-shrinkwrap.json</code> may be included when publishing a package.</p>
|
||||
<p>The recommended use-case for <code>npm-shrinkwrap.json</code> is applications deployed
|
||||
through the publishing process on the registry: for example, daemons and
|
||||
command-line tools intended as global installs or <code>devDependencies</code>. It's
|
||||
strongly discouraged for library authors to publish this file, since that would
|
||||
prevent end users from having control over transitive dependency updates.</p>
|
||||
<p>Additionally, if both <code>package-lock.json</code> and <code>npm-shrinwkrap.json</code> are present
|
||||
<p>Additionally, if both <code>package-lock.json</code> and <code>npm-shrinkwrap.json</code> are present
|
||||
in a package root, <code>package-lock.json</code> will be ignored in favor of this file.</p>
|
||||
<p>For full details and description of the <code>npm-shrinkwrap.json</code> file format, refer
|
||||
to the manual page for <a href="../files/package-lock.json.html">package-lock.json(5)</a>.</p>
|
||||
@ -42,4 +42,4 @@ to the manual page for <a href="../files/package-lock.json.html">package-lock.js
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-shrinkwrap.json — npm@5.0.3</p>
|
||||
<p id="footer">npm-shrinkwrap.json — npm@5.3.0</p>
|
||||
|
||||
2
deps/npm/html/doc/files/npmrc.html
vendored
2
deps/npm/html/doc/files/npmrc.html
vendored
@ -85,5 +85,5 @@ manner.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npmrc — npm@5.0.3</p>
|
||||
<p id="footer">npmrc — npm@5.3.0</p>
|
||||
|
||||
|
||||
@ -108,7 +108,7 @@ on the current platform.</p>
|
||||
<h2 id="see-also">SEE ALSO</h2>
|
||||
<ul>
|
||||
<li><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></li>
|
||||
<li><a href="../files/package-lock.json.html">package-lock.json(5)</a></li>
|
||||
<li><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></li>
|
||||
<li><a href="../files/package.json.html">package.json(5)</a></li>
|
||||
<li><a href="../cli/npm-install.html">npm-install(1)</a></li>
|
||||
</ul>
|
||||
@ -124,4 +124,4 @@ on the current platform.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">package-lock.json — npm@5.0.3</p>
|
||||
<p id="footer">package-lock.json — npm@5.3.0</p>
|
||||
|
||||
38
deps/npm/html/doc/files/package.json.html
vendored
38
deps/npm/html/doc/files/package.json.html
vendored
@ -342,15 +342,22 @@ tarball or git URL.</p>
|
||||
<p>This tarball will be downloaded and installed locally to your package at
|
||||
install time.</p>
|
||||
<h3 id="git-urls-as-dependencies">Git URLs as Dependencies</h3>
|
||||
<p>Git urls can be of the form:</p>
|
||||
<pre><code>git://github.com/user/project.git#commit-ish
|
||||
git+ssh://user@hostname:project.git#commit-ish
|
||||
git+ssh://user@hostname/project.git#commit-ish
|
||||
git+http://user@hostname/project/blah.git#commit-ish
|
||||
git+https://user@hostname/project/blah.git#commit-ish
|
||||
</code></pre><p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as
|
||||
an argument to <code>git checkout</code>. The default is <code>master</code>.</p>
|
||||
<h2 id="github-urls">GitHub URLs</h2>
|
||||
<p>Git urls are of the form:</p>
|
||||
<pre><code><protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
|
||||
</code></pre><p><code><protocol></code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, <code>git+https</code>, or
|
||||
<code>git+file</code>.</p>
|
||||
<p>If <code>#<commit-ish></code> is provided, it will be used to clone exactly that
|
||||
commit. If the commit-ish has the format <code>#semver:<semver></code>, <code><semver></code> can
|
||||
be any valid semver range or exact version, and npm will look for any tags
|
||||
or refs matching that range in the remote repository, much as it would for a
|
||||
registry dependency. If neither <code>#<commit-ish></code> or <code>#semver:<semver></code> is
|
||||
specified, then <code>master</code> is used.</p>
|
||||
<p>Examples:</p>
|
||||
<pre><code>git+ssh://git@github.com:npm/npm.git#v1.0.27
|
||||
git+ssh://git@github.com:npm/npm#semver:^5.0
|
||||
git+https://isaacs@github.com/npm/npm.git
|
||||
git://github.com/npm/npm.git#v1.0.27
|
||||
</code></pre><h3 id="github-urls">GitHub URLs</h3>
|
||||
<p>As of version 1.1.65, you can refer to GitHub urls as just "foo":
|
||||
"user/foo-project". Just as with git URLs, a <code>commit-ish</code> suffix can be
|
||||
included. For example:</p>
|
||||
@ -363,7 +370,7 @@ included. For example:</p>
|
||||
"module": "user/repo#feature\/branch"
|
||||
}
|
||||
}
|
||||
</code></pre><h2 id="local-paths">Local Paths</h2>
|
||||
</code></pre><h3 id="local-paths">Local Paths</h3>
|
||||
<p>As of version 2.0.0 you can provide a path to a local directory that contains a
|
||||
package. Local paths can be saved using <code>npm install -S</code> or
|
||||
<code>npm install --save</code>, using any of these forms:</p>
|
||||
@ -523,11 +530,10 @@ you can specify which ones.</p>
|
||||
<pre><code>"cpu" : [ "!arm", "!mips" ]
|
||||
</code></pre><p>The host architecture is determined by <code>process.arch</code></p>
|
||||
<h2 id="preferglobal">preferGlobal</h2>
|
||||
<p>If your package is primarily a command-line application that should be
|
||||
installed globally, then set this value to <code>true</code> to provide a warning
|
||||
if it is installed locally.</p>
|
||||
<p>It doesn't actually prevent users from installing it locally, but it
|
||||
does help prevent some confusion if it doesn't work as expected.</p>
|
||||
<p><strong>DEPRECATED</strong></p>
|
||||
<p>This option used to trigger an npm warning, but it will no longer warn. It is
|
||||
purely there for informational purposes. It is now recommended that you install
|
||||
any binaries as local devDependencies wherever possible.</p>
|
||||
<h2 id="private">private</h2>
|
||||
<p>If you set <code>"private": true</code> in your package.json, then npm will refuse
|
||||
to publish it.</p>
|
||||
@ -587,5 +593,5 @@ ignored.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">package.json — npm@5.0.3</p>
|
||||
<p id="footer">package.json — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/index.html
vendored
2
deps/npm/html/doc/index.html
vendored
@ -168,5 +168,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-index — npm@5.0.3</p>
|
||||
<p id="footer">npm-index — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-coding-style.html
vendored
2
deps/npm/html/doc/misc/npm-coding-style.html
vendored
@ -153,5 +153,5 @@ set to anything."</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-coding-style — npm@5.0.3</p>
|
||||
<p id="footer">npm-coding-style — npm@5.3.0</p>
|
||||
|
||||
|
||||
23
deps/npm/html/doc/misc/npm-config.html
vendored
23
deps/npm/html/doc/misc/npm-config.html
vendored
@ -15,8 +15,13 @@
|
||||
<h3 id="command-line-flags">Command Line Flags</h3>
|
||||
<p>Putting <code>--foo bar</code> on the command line sets the <code>foo</code> configuration
|
||||
parameter to <code>"bar"</code>. A <code>--</code> argument tells the cli parser to stop
|
||||
reading flags. A <code>--flag</code> parameter that is at the <em>end</em> of the
|
||||
command will be given the value of <code>true</code>.</p>
|
||||
reading flags. Using <code>--flag</code> without specifying any value will set
|
||||
the value to <code>true</code>.</p>
|
||||
<p>Example: <code>--flag1 --flag2</code> will set both configuration parameters
|
||||
to <code>true</code>, while <code>--flag1 --flag2 bar</code> will set <code>flag1</code> to <code>true</code>,
|
||||
and <code>flag2</code> to <code>bar</code>. Finally, <code>--flag1 --flag2 -- bar</code> will set
|
||||
both configuration parameters to <code>true</code>, and the <code>bar</code> is taken
|
||||
as a command argument.</p>
|
||||
<h3 id="environment-variables">Environment Variables</h3>
|
||||
<p>Any environment variables that start with <code>npm_config_</code> will be
|
||||
interpreted as a configuration parameter. For example, putting
|
||||
@ -25,7 +30,7 @@ configuration parameter to <code>bar</code>. Any environment configurations tha
|
||||
are not given a value will be given the value of <code>true</code>. Config
|
||||
values are case-insensitive, so <code>NPM_CONFIG_FOO=bar</code> will work the
|
||||
same. However, please note that inside <a href="/misc/scripts">npm-scripts</a>
|
||||
npm will set it's own environment variables and Node will prefer
|
||||
npm will set its own environment variables and Node will prefer
|
||||
those lowercase versions over any uppercase ones that you might set.
|
||||
For details see <a href="https://github.com/npm/npm/issues/14528">this issue</a>.</p>
|
||||
<h3 id="npmrc-files">npmrc Files</h3>
|
||||
@ -33,9 +38,9 @@ For details see <a href="https://github.com/npm/npm/issues/14528">this issue</a>
|
||||
<ul>
|
||||
<li>per-project configuration file (<code>/path/to/my/project/.npmrc</code>)</li>
|
||||
<li>per-user configuration file (defaults to <code>$HOME/.npmrc</code>; configurable via CLI
|
||||
option <code>--userconfig</code> or environment variable <code>$NPM_CONF_USERCONFIG</code>)</li>
|
||||
option <code>--userconfig</code> or environment variable <code>$NPM_CONFIG_USERCONFIG</code>)</li>
|
||||
<li>global configuration file (defaults to <code>$PREFIX/etc/npmrc</code>; configurable via
|
||||
CLI option <code>--globalconfig</code> or environment variable <code>$NPM_CONF_GLOBALCONFIG</code>)</li>
|
||||
CLI option <code>--globalconfig</code> or environment variable <code>$NPM_CONFIG_GLOBALCONFIG</code>)</li>
|
||||
<li>npm's built-in configuration file (<code>/path/to/npm/npmrc</code>)</li>
|
||||
</ul>
|
||||
<p>See <a href="../files/npmrc.html">npmrc(5)</a> for more details.</p>
|
||||
@ -756,6 +761,12 @@ in to a private registry for the first time:
|
||||
<code>npm login --scope=@organization --registry=registry.organization.com</code>, which
|
||||
will cause <code>@organization</code> to be mapped to the registry for future installation
|
||||
of packages specified according to the pattern <code>@organization/package</code>.</p>
|
||||
<h3 id="script-shell">script-shell</h3>
|
||||
<ul>
|
||||
<li>Default: <code>null</code></li>
|
||||
<li>Type: path</li>
|
||||
</ul>
|
||||
<p>The shell to use for scripts run with the <code>npm run</code> command.</p>
|
||||
<h3 id="scripts-prepend-node-path">scripts-prepend-node-path</h3>
|
||||
<ul>
|
||||
<li>Default: "warn-only"</li>
|
||||
@ -981,5 +992,5 @@ exit successfully.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-config — npm@5.0.3</p>
|
||||
<p id="footer">npm-config — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-developers.html
vendored
2
deps/npm/html/doc/misc/npm-developers.html
vendored
@ -194,5 +194,5 @@ from a fresh checkout.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-developers — npm@5.0.3</p>
|
||||
<p id="footer">npm-developers — npm@5.3.0</p>
|
||||
|
||||
|
||||
12
deps/npm/html/doc/misc/npm-disputes.html
vendored
12
deps/npm/html/doc/misc/npm-disputes.html
vendored
@ -20,7 +20,7 @@ Conduct.</p>
|
||||
<h2 id="tl-dr">TL;DR</h2>
|
||||
<ol>
|
||||
<li>Get the author email with <code>npm owner ls <pkgname></code></li>
|
||||
<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li>
|
||||
<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li>
|
||||
<li>After a few weeks, if there's no resolution, we'll sort it out.</li>
|
||||
</ol>
|
||||
<p>Don't squat on package names. Publish code or move out of the way.</p>
|
||||
@ -55,12 +55,12 @@ because Yusuf's <code>foo</code> is in the way.</p>
|
||||
</li>
|
||||
<li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>,
|
||||
and what she would like to do with the module name. She adds the npm support
|
||||
staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email
|
||||
staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email
|
||||
that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the
|
||||
foo package.</li>
|
||||
<li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf
|
||||
and Alice can't come to any sort of resolution, email support
|
||||
<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least
|
||||
<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least
|
||||
4 weeks.)</li>
|
||||
</ol>
|
||||
<h2 id="reasoning">REASONING</h2>
|
||||
@ -96,12 +96,12 @@ application database or otherwise putting non-packagey things into it.</li>
|
||||
<a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful
|
||||
language, pornographic content, or harassment.</li>
|
||||
</ol>
|
||||
<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right
|
||||
<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right
|
||||
away. <strong>You are never expected to resolve abusive behavior on your own. We are
|
||||
here to help.</strong></p>
|
||||
<h2 id="trademarks">TRADEMARKS</h2>
|
||||
<p>If you think another npm publisher is infringing your trademark, such as by
|
||||
using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to
|
||||
using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to
|
||||
the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a
|
||||
copy of your trademark registration certificate.</p>
|
||||
<p>If we see that the package's publisher is intentionally misleading others by
|
||||
@ -134,5 +134,5 @@ License.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-disputes — npm@5.0.3</p>
|
||||
<p id="footer">npm-disputes — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-index.html
vendored
2
deps/npm/html/doc/misc/npm-index.html
vendored
@ -168,5 +168,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-index — npm@5.0.3</p>
|
||||
<p id="footer">npm-index — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-orgs.html
vendored
2
deps/npm/html/doc/misc/npm-orgs.html
vendored
@ -86,5 +86,5 @@
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-orgs — npm@5.0.3</p>
|
||||
<p id="footer">npm-orgs — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-registry.html
vendored
2
deps/npm/html/doc/misc/npm-registry.html
vendored
@ -90,5 +90,5 @@ effectively implement the entire CouchDB API anyway.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-registry — npm@5.0.3</p>
|
||||
<p id="footer">npm-registry — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/npm-scope.html
vendored
2
deps/npm/html/doc/misc/npm-scope.html
vendored
@ -99,5 +99,5 @@ that registry instead.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-scope — npm@5.0.3</p>
|
||||
<p id="footer">npm-scope — npm@5.3.0</p>
|
||||
|
||||
|
||||
6
deps/npm/html/doc/misc/npm-scripts.html
vendored
6
deps/npm/html/doc/misc/npm-scripts.html
vendored
@ -74,10 +74,6 @@ event has been introduced, <code>prepare</code>, that preserves this existing be
|
||||
allow users to avoid the confusing behavior of existing npm versions and only
|
||||
run on <code>npm publish</code> (for instance, running the tests one last time to ensure
|
||||
they're in good shape).</p>
|
||||
<p><strong>IMPORTANT:</strong> As of <code>npm@5</code>, <code>prepublish</code> will <em>only</em> be run for <code>npm
|
||||
publish</code>. This will make its behavior identical to <code>prepublishOnly</code>, so
|
||||
<code>npm@6</code> or later may drop support for the use of <code>prepublishOnly</code>, and then
|
||||
maybe we can all forget this embarrassing thing ever happened.</p>
|
||||
<p>See <a href="https://github.com/npm/npm/issues/10074">https://github.com/npm/npm/issues/10074</a> for a much lengthier
|
||||
justification, with further reading, for this change.</p>
|
||||
<h3 id="use-cases">USE CASES</h3>
|
||||
@ -243,5 +239,5 @@ scripts is for compilation which must be done on the target architecture.</li>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">npm-scripts — npm@5.0.3</p>
|
||||
<p id="footer">npm-scripts — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/removing-npm.html
vendored
2
deps/npm/html/doc/misc/removing-npm.html
vendored
@ -57,5 +57,5 @@ modules. To track those down, you can do the following:</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">removing-npm — npm@5.0.3</p>
|
||||
<p id="footer">removing-npm — npm@5.3.0</p>
|
||||
|
||||
|
||||
2
deps/npm/html/doc/misc/semver.html
vendored
2
deps/npm/html/doc/misc/semver.html
vendored
@ -325,5 +325,5 @@ range, use the <code>satisfies(version, range)</code> function.</p>
|
||||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr>
|
||||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr>
|
||||
</table>
|
||||
<p id="footer">semver — npm@5.0.3</p>
|
||||
<p id="footer">semver — npm@5.3.0</p>
|
||||
|
||||
|
||||
72
deps/npm/lib/build.js
vendored
72
deps/npm/lib/build.js
vendored
@ -43,14 +43,23 @@ function build (args, global, didPre, didRB, cb) {
|
||||
global = npm.config.get('global')
|
||||
}
|
||||
|
||||
// it'd be nice to asyncMap these, but actually, doing them
|
||||
// in parallel generally munges up the output from node-waf
|
||||
var builder = build_(global, didPre, didRB)
|
||||
chain(args.map(function (arg) {
|
||||
return function (cb) {
|
||||
builder(arg, cb)
|
||||
}
|
||||
}), cb)
|
||||
if (!args.length) {
|
||||
readJson(path.resolve(npm.localPrefix, 'package.json'), function (er, pkg) {
|
||||
if (!args.length && pkg && pkg.scripts && pkg.scripts.build) {
|
||||
log.warn('build', '`npm build` called with no arguments. Did you mean to `npm run-script build`?')
|
||||
}
|
||||
cb()
|
||||
})
|
||||
} else {
|
||||
// it'd be nice to asyncMap these, but actually, doing them
|
||||
// in parallel generally munges up the output from node-waf
|
||||
var builder = build_(global, didPre, didRB)
|
||||
chain(args.map(function (arg) {
|
||||
return function (cb) {
|
||||
builder(arg, cb)
|
||||
}
|
||||
}), cb)
|
||||
}
|
||||
}
|
||||
|
||||
function build_ (global, didPre, didRB) {
|
||||
@ -108,44 +117,15 @@ var linkStuff = build.linkStuff = function (pkg, folder, global, didRB, cb) {
|
||||
if (gnm) log.silly('linkStuff', packageId(pkg), 'is installed into a global node_modules')
|
||||
if (gtop) log.silly('linkStuff', packageId(pkg), 'is installed into the top-level global node_modules')
|
||||
|
||||
shouldWarn(pkg, folder, global, function () {
|
||||
asyncMap(
|
||||
[linkBins, linkMans, !didRB && rebuildBundles],
|
||||
function (fn, cb) {
|
||||
if (!fn) return cb()
|
||||
log.verbose(fn.name, packageId(pkg))
|
||||
fn(pkg, folder, parent, gtop, cb)
|
||||
},
|
||||
cb
|
||||
)
|
||||
})
|
||||
}
|
||||
|
||||
function shouldWarn (pkg, folder, global, cb) {
|
||||
var parent = path.dirname(folder)
|
||||
var top = parent === npm.dir
|
||||
var cwd = npm.localPrefix
|
||||
|
||||
readJson(path.resolve(cwd, 'package.json'), function (er, topPkg) {
|
||||
if (er) return cb(er)
|
||||
|
||||
var linkedPkg = path.basename(cwd)
|
||||
var currentPkg = path.basename(folder)
|
||||
|
||||
// current searched package is the linked package on first call
|
||||
if (linkedPkg !== currentPkg) {
|
||||
// don't generate a warning if it's listed in dependencies
|
||||
if (Object.keys(topPkg.dependencies || {})
|
||||
.concat(Object.keys(topPkg.devDependencies || {}))
|
||||
.indexOf(currentPkg) === -1) {
|
||||
if (top && pkg.preferGlobal && !global) {
|
||||
log.warn('prefer global', packageId(pkg) + ' should be installed with -g')
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
cb()
|
||||
})
|
||||
asyncMap(
|
||||
[linkBins, linkMans, !didRB && rebuildBundles],
|
||||
function (fn, cb) {
|
||||
if (!fn) return cb()
|
||||
log.verbose(fn.name, packageId(pkg))
|
||||
fn(pkg, folder, parent, gtop, cb)
|
||||
},
|
||||
cb
|
||||
)
|
||||
}
|
||||
|
||||
function rebuildBundles (pkg, folder, parent, gtop, cb) {
|
||||
|
||||
8
deps/npm/lib/config/cmd-list.js
vendored
8
deps/npm/lib/config/cmd-list.js
vendored
@ -1,5 +1,3 @@
|
||||
var extend = Object.assign || require('util')._extend
|
||||
|
||||
// short names for common things
|
||||
var shorthands = {
|
||||
'un': 'uninstall',
|
||||
@ -29,6 +27,7 @@ var affordances = {
|
||||
'apihelp': 'help',
|
||||
'find-dupes': 'dedupe',
|
||||
'upgrade': 'update',
|
||||
'udpate': 'update',
|
||||
'login': 'adduser',
|
||||
'add-user': 'adduser',
|
||||
'author': 'owner',
|
||||
@ -41,7 +40,8 @@ var affordances = {
|
||||
'unlink': 'uninstall',
|
||||
'remove': 'uninstall',
|
||||
'rm': 'uninstall',
|
||||
'r': 'uninstall'
|
||||
'r': 'uninstall',
|
||||
'rum': 'run-script'
|
||||
}
|
||||
|
||||
// these are filenames in .
|
||||
@ -110,7 +110,7 @@ var plumbing = [
|
||||
'substack',
|
||||
'visnup'
|
||||
]
|
||||
module.exports.aliases = extend(extend({}, shorthands), affordances)
|
||||
module.exports.aliases = Object.assign({}, shorthands, affordances)
|
||||
module.exports.shorthands = shorthands
|
||||
module.exports.affordances = affordances
|
||||
module.exports.cmdList = cmdList
|
||||
|
||||
2
deps/npm/lib/config/defaults.js
vendored
2
deps/npm/lib/config/defaults.js
vendored
@ -203,6 +203,7 @@ Object.defineProperty(exports, 'defaults', {get: function () {
|
||||
'save-prefix': '^',
|
||||
'save-prod': false,
|
||||
scope: '',
|
||||
'script-shell': null,
|
||||
'scripts-prepend-node-path': 'warn-only',
|
||||
searchopts: '',
|
||||
searchexclude: null,
|
||||
@ -326,6 +327,7 @@ exports.types = {
|
||||
'save-prefix': String,
|
||||
'save-prod': Boolean,
|
||||
scope: String,
|
||||
'script-shell': [null, String],
|
||||
'scripts-prepend-node-path': [false, true, 'auto', 'warn-only'],
|
||||
searchopts: String,
|
||||
searchexclude: [null, String],
|
||||
|
||||
@ -36,8 +36,6 @@ function getCredentialsByURI (uri) {
|
||||
|
||||
// Handle the old-style _auth=<base64> style for the default
|
||||
// registry, if set.
|
||||
//
|
||||
// XXX(isaacs): Remove when npm 1.4 is no longer relevant
|
||||
var authDef = this.get('_auth')
|
||||
var userDef = this.get('username')
|
||||
var passDef = this.get('_password')
|
||||
|
||||
53
deps/npm/lib/config/pacote.js
vendored
53
deps/npm/lib/config/pacote.js
vendored
@ -47,40 +47,63 @@ function pacoteOpts (moreOpts) {
|
||||
},
|
||||
scope: npm.config.get('scope'),
|
||||
strictSSL: npm.config.get('strict-ssl'),
|
||||
userAgent: npm.config.get('user-agent')
|
||||
userAgent: npm.config.get('user-agent'),
|
||||
|
||||
dmode: npm.modes.exec,
|
||||
fmode: npm.modes.file,
|
||||
umask: npm.modes.umask
|
||||
}
|
||||
|
||||
if (ownerStats.uid || ownerStats.gid) {
|
||||
if (ownerStats.uid != null || ownerStats.gid != null) {
|
||||
Object.assign(opts, ownerStats)
|
||||
}
|
||||
|
||||
npm.config.keys.forEach(function (k) {
|
||||
const authMatch = k[0] === '/' && k.match(
|
||||
/(.*):(_authToken|username|_password|password|email|always-auth)$/
|
||||
const authMatchGlobal = k.match(
|
||||
/^(_authToken|username|_password|password|email|always-auth|_auth)$/
|
||||
)
|
||||
if (authMatch) {
|
||||
const nerfDart = authMatch[1]
|
||||
const key = authMatch[2]
|
||||
const val = npm.config.get(k)
|
||||
const authMatchScoped = k[0] === '/' && k.match(
|
||||
/(.*):(_authToken|username|_password|password|email|always-auth|_auth)$/
|
||||
)
|
||||
|
||||
// if it matches scoped it will also match global
|
||||
if (authMatchGlobal || authMatchScoped) {
|
||||
let nerfDart = null
|
||||
let key = null
|
||||
let val = null
|
||||
|
||||
if (!opts.auth) { opts.auth = {} }
|
||||
if (!opts.auth[nerfDart]) {
|
||||
opts.auth[nerfDart] = {
|
||||
alwaysAuth: !!npm.config.get('always-auth')
|
||||
|
||||
if (authMatchScoped) {
|
||||
nerfDart = authMatchScoped[1]
|
||||
key = authMatchScoped[2]
|
||||
val = npm.config.get(k)
|
||||
if (!opts.auth[nerfDart]) {
|
||||
opts.auth[nerfDart] = {
|
||||
alwaysAuth: !!npm.config.get('always-auth')
|
||||
}
|
||||
}
|
||||
} else {
|
||||
key = authMatchGlobal[1]
|
||||
val = npm.config.get(k)
|
||||
opts.auth.alwaysAuth = !!npm.config.get('always-auth')
|
||||
}
|
||||
|
||||
const auth = authMatchScoped ? opts.auth[nerfDart] : opts.auth
|
||||
if (key === '_authToken') {
|
||||
opts.auth[nerfDart].token = val
|
||||
auth.token = val
|
||||
} else if (key.match(/password$/i)) {
|
||||
opts.auth[nerfDart].password =
|
||||
auth.password =
|
||||
// the config file stores password auth already-encoded. pacote expects
|
||||
// the actual username/password pair.
|
||||
Buffer.from(val, 'base64').toString('utf8')
|
||||
} else if (key === 'always-auth') {
|
||||
opts.auth[nerfDart].alwaysAuth = val === 'false' ? false : !!val
|
||||
auth.alwaysAuth = val === 'false' ? false : !!val
|
||||
} else {
|
||||
opts.auth[nerfDart][key] = val
|
||||
auth[key] = val
|
||||
}
|
||||
}
|
||||
|
||||
if (k[0] === '@') {
|
||||
if (!opts.scopeTargets) { opts.scopeTargets = {} }
|
||||
opts.scopeTargets[k.replace(/:registry$/, '')] = npm.config.get(k)
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user