From 24f43903b4a2f5aa73a99e6f3d4cc62d559cf94b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kat=20March=C3=A1n?=
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. Whoever responds will no
+doubt tell you to put the output in a gist or email.
package.json
in the current folder and use the name
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.
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.
npm config delete key
Deletes the key from all configuration files.
@@ -67,5 +67,5 @@ global config.v
.
name
property.
npm cache clean
and reset the cache.
"notepad"
on Windows.
npm install
.
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.
The --only={prod[uction]|dev[elopment]}
argument will cause either only
@@ -365,5 +367,5 @@ affects a real use-case, it will be investigated.
npm ls promzard
in npm's source tree will show:
-npm@5.0.3 /path/to/npm
+npm@5.3.0 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
It will print out extraneous, missing, and invalid packages.
@@ -80,6 +80,12 @@ project.
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)
@@ -104,5 +110,5 @@ project.
-
+
diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html
index 1c862a8ba7..b25aaec3d3 100644
--- a/deps/npm/html/doc/cli/npm-outdated.html
+++ b/deps/npm/html/doc/cli/npm-outdated.html
@@ -116,5 +116,5 @@ project.
-
+
diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html
index e4cc4d7de8..7b9980c67c 100644
--- a/deps/npm/html/doc/cli/npm-owner.html
+++ b/deps/npm/html/doc/cli/npm-owner.html
@@ -51,5 +51,5 @@ that is not implemented at this time.
-
+
diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html
index 25982014e3..2d66916d8b 100644
--- a/deps/npm/html/doc/cli/npm-pack.html
+++ b/deps/npm/html/doc/cli/npm-pack.html
@@ -41,5 +41,5 @@ overwritten the second time.
-
+
diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html
index 666ba97c7c..68a5e85749 100644
--- a/deps/npm/html/doc/cli/npm-ping.html
+++ b/deps/npm/html/doc/cli/npm-ping.html
@@ -32,5 +32,5 @@
-
+
diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html
index 30c3172493..2560340d5e 100644
--- a/deps/npm/html/doc/cli/npm-prefix.html
+++ b/deps/npm/html/doc/cli/npm-prefix.html
@@ -38,5 +38,5 @@ to contain a package.json file unless -g
is also specified.
-
+
diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html
index 52b2ba78e4..a7073a9e02 100644
--- a/deps/npm/html/doc/cli/npm-prune.html
+++ b/deps/npm/html/doc/cli/npm-prune.html
@@ -40,5 +40,5 @@ negate NODE_ENV
being set to production
.
-
+
diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html
index 3fca992169..2d3b1d1db8 100644
--- a/deps/npm/html/doc/cli/npm-publish.html
+++ b/deps/npm/html/doc/cli/npm-publish.html
@@ -79,5 +79,5 @@ packs them into a tarball to be uploaded to the registry.
-
+
diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html
index 7ec9923cb8..bc8ee78771 100644
--- a/deps/npm/html/doc/cli/npm-rebuild.html
+++ b/deps/npm/html/doc/cli/npm-rebuild.html
@@ -35,5 +35,5 @@ the new binary.
-
+
diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html
index 38990dc8e9..e2ef9ee958 100644
--- a/deps/npm/html/doc/cli/npm-repo.html
+++ b/deps/npm/html/doc/cli/npm-repo.html
@@ -41,5 +41,5 @@ a package.json
in the current folder and use the name
-
+
diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html
index 6847b24387..a6648c5716 100644
--- a/deps/npm/html/doc/cli/npm-restart.html
+++ b/deps/npm/html/doc/cli/npm-restart.html
@@ -53,5 +53,5 @@ behavior will be accompanied by an increase in major version number
-
+
diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html
index af03619a5d..94b59687ab 100644
--- a/deps/npm/html/doc/cli/npm-root.html
+++ b/deps/npm/html/doc/cli/npm-root.html
@@ -35,5 +35,5 @@
-
+
diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html
index 2f61d63aec..037ad1a64c 100644
--- a/deps/npm/html/doc/cli/npm-run-script.html
+++ b/deps/npm/html/doc/cli/npm-run-script.html
@@ -11,7 +11,7 @@
npm-run-script
Run arbitrary package scripts
SYNOPSIS
-
npm run-script <command> [-- <args>...]
+npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
@@ -46,6 +46,7 @@ default in npm
v3), this is only performed when that nodePATH
.
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)
@@ -66,5 +67,5 @@ you will be given a warning to run npm install
, just in case you
-
+
diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html
index cc95846328..e136612e96 100644
--- a/deps/npm/html/doc/cli/npm-search.html
+++ b/deps/npm/html/doc/cli/npm-search.html
@@ -109,5 +109,5 @@ setting.
-
+
diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html
index 44388546d8..c68795a33f 100644
--- a/deps/npm/html/doc/cli/npm-shrinkwrap.html
+++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html
@@ -41,5 +41,5 @@ of package locks in npm, see npm-packa
-
+
diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html
index aacae89361..7f16258c09 100644
--- a/deps/npm/html/doc/cli/npm-star.html
+++ b/deps/npm/html/doc/cli/npm-star.html
@@ -36,5 +36,5 @@ a vaguely positive way to show that you care.
-
+
diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html
index 8252aa8f21..cac0603d22 100644
--- a/deps/npm/html/doc/cli/npm-stars.html
+++ b/deps/npm/html/doc/cli/npm-stars.html
@@ -36,5 +36,5 @@ you will most certainly enjoy this command.
-
+
diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html
index 8c8dd3bb39..0322627378 100644
--- a/deps/npm/html/doc/cli/npm-start.html
+++ b/deps/npm/html/doc/cli/npm-start.html
@@ -39,5 +39,5 @@ more details.
-
+
diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html
index b55a285de7..ac2e46f74a 100644
--- a/deps/npm/html/doc/cli/npm-stop.html
+++ b/deps/npm/html/doc/cli/npm-stop.html
@@ -34,5 +34,5 @@
-
+
diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html
index 8bf5fdea1e..a80d86c3ad 100644
--- a/deps/npm/html/doc/cli/npm-team.html
+++ b/deps/npm/html/doc/cli/npm-team.html
@@ -67,5 +67,5 @@ use the npm access
command to grant or revoke the appropriate permi
-
+
diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html
index e099df218c..ecbbc74b9a 100644
--- a/deps/npm/html/doc/cli/npm-test.html
+++ b/deps/npm/html/doc/cli/npm-test.html
@@ -36,5 +36,5 @@
-
+
diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html
index 37bb0bd71f..5e60ae3038 100644
--- a/deps/npm/html/doc/cli/npm-uninstall.html
+++ b/deps/npm/html/doc/cli/npm-uninstall.html
@@ -11,7 +11,7 @@
npm-uninstall
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
DESCRIPTION
@@ -30,6 +30,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 @@ well.
npm uninstall @myorg/privatepackage --save
npm uninstall node-tap --save-dev
npm uninstall dtrace-provider --save-optional
+npm uninstall lodash --no-save
SEE ALSO
- npm-prune(1)
@@ -60,5 +63,5 @@ npm uninstall dtrace-provider --save-optional
-
+
diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html
index 36d0d32861..220efe599a 100644
--- a/deps/npm/html/doc/cli/npm-unpublish.html
+++ b/deps/npm/html/doc/cli/npm-unpublish.html
@@ -51,5 +51,5 @@ contact support@npmjs.com.
-
+
diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html
index 197aa41870..471db2baba 100644
--- a/deps/npm/html/doc/cli/npm-update.html
+++ b/deps/npm/html/doc/cli/npm-update.html
@@ -118,5 +118,5 @@ be downgraded.
-
+
diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html
index bc29ed75ac..e821d71fc6 100644
--- a/deps/npm/html/doc/cli/npm-version.html
+++ b/deps/npm/html/doc/cli/npm-version.html
@@ -114,5 +114,5 @@ to the same value as the current version.
-
+
diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html
index 70bf31e435..9d30ff9031 100644
--- a/deps/npm/html/doc/cli/npm-view.html
+++ b/deps/npm/html/doc/cli/npm-view.html
@@ -86,5 +86,5 @@ the field name.
-
+
diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html
index 8f84bc8ab6..9c8b91e4d5 100644
--- a/deps/npm/html/doc/cli/npm-whoami.html
+++ b/deps/npm/html/doc/cli/npm-whoami.html
@@ -33,5 +33,5 @@
-
+
diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html
index 4e4d97b235..06414eebab 100644
--- a/deps/npm/html/doc/cli/npm.html
+++ b/deps/npm/html/doc/cli/npm.html
@@ -13,7 +13,7 @@
SYNOPSIS
npm <command> [args]
VERSION
-5.0.3
+5.3.0
DESCRIPTION
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.
Isaac Z. Schlueter ::
isaacs ::
@izs ::
-i@izs.me
+i@izs.me
SEE ALSO
- npm-help(1)
@@ -150,5 +150,5 @@ will no doubt tell you to put the output in a gist or email.
-
+
diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html
index 300df680e1..915750606c 100644
--- a/deps/npm/html/doc/files/npm-folders.html
+++ b/deps/npm/html/doc/files/npm-folders.html
@@ -25,10 +25,9 @@ is installed.
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
current working directory if not in a package already.
@@ -182,5 +181,5 @@ cannot be found elsewhere. See packa
-
+
diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html
index 300df680e1..915750606c 100644
--- a/deps/npm/html/doc/files/npm-global.html
+++ b/deps/npm/html/doc/files/npm-global.html
@@ -25,10 +25,9 @@ is installed.
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
current working directory if not in a package already.
@@ -182,5 +181,5 @@ cannot be found elsewhere. See packa
-
+
diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html
index e0f2df86f2..6374cc5a7d 100644
--- a/deps/npm/html/doc/files/npm-json.html
+++ b/deps/npm/html/doc/files/npm-json.html
@@ -342,15 +342,22 @@ tarball or git URL.
This tarball will be downloaded and installed locally to your package at
install time.
Git URLs as Dependencies
-Git urls can be 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
-
The commit-ish
can be any tag, sha, or branch which can be supplied as
-an argument to git checkout
. The default is master
.
-GitHub URLs
+Git urls are of the form:
+<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
+
<protocol>
is one of git
, git+ssh
, git+http
, git+https
, or
+git+file
.
+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
included. For example:
@@ -363,7 +370,7 @@ included. For example:
"module": "user/repo#feature\/branch"
}
}
-
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
npm install --save
, using any of these forms:
"cpu" : [ "!arm", "!mips" ]
The host architecture is determined by process.arch
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.
It doesn't actually prevent users from installing it locally, but it -does help prevent some confusion if it doesn't work as expected.
+DEPRECATED
+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.
If you set "private": true
in your package.json, then npm will refuse
to publish it.
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
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
to the manual page for package-lock.json(5).
This tarball will be downloaded and installed locally to your package at install time.
Git urls can be 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
-
The commit-ish
can be any tag, sha, or branch which can be supplied as
-an argument to git checkout
. The default is master
.
Git urls are of the form:
+<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
+
<protocol>
is one of git
, git+ssh
, git+http
, git+https
, or
+git+file
.
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
+
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
included. For example:
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
npm install --save
, using any of these forms:
"cpu" : [ "!arm", "!mips" ]
The host architecture is determined by process.arch
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.
It doesn't actually prevent users from installing it locally, but it -does help prevent some confusion if it doesn't work as expected.
+DEPRECATED
+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.
If you set "private": true
in your package.json, then npm will refuse
to publish it.
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
.
--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.
Any environment variables that start with npm_config_
will be
interpreted as a configuration parameter. For example, putting
@@ -25,7 +30,7 @@ configuration parameter to bar
. Any environment configurations tha
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
-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.
/path/to/my/project/.npmrc
)$HOME/.npmrc
; configurable via CLI
-option --userconfig
or environment variable $NPM_CONF_USERCONFIG
)--userconfig
or environment variable $NPM_CONFIG_USERCONFIG
)
$PREFIX/etc/npmrc
; configurable via
-CLI option --globalconfig
or environment variable $NPM_CONF_GLOBALCONFIG
)--globalconfig
or environment variable $NPM_CONFIG_GLOBALCONFIG
)
/path/to/npm/npmrc
)See npmrc(5) for more details.
@@ -756,6 +761,12 @@ in to a private registry for the first time:npm login --scope=@organization --registry=registry.organization.com
, which
will cause @organization
to be mapped to the registry for future installation
of packages specified according to the pattern @organization/package
.
+null
The shell to use for scripts run with the npm run
command.
npm owner ls <pkgname>
Don't squat on package names. Publish code or move out of the way.
@@ -55,12 +55,12 @@ because Yusuf'sfoo
is in the way.
add alice foo
to add Alice as an owner of the
foo package.If you see bad behavior like this, please report it to abuse@npmjs.com right +
If you see bad behavior like this, please report it to abuse@npmjs.com right away. You are never expected to resolve abusive behavior on your own. We are here to help.
If you think another npm publisher is infringing your trademark, such as by -using a confusingly similar package name, email abuse@npmjs.com with a link to +using a confusingly similar package name, email abuse@npmjs.com with a link to the package or user account on https://npmjs.com. Attach a copy of your trademark registration certificate.
If we see that the package's publisher is intentionally misleading others by @@ -134,5 +134,5 @@ License.
prepare
, that preserves this existing be
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.
satisfies(version, range)
function.