npm-install

Install a package

Select CLI Version:

See Details

Table of contents

Synopsis

npminstall(with no args,in packagedir)
npminstall[<@scope>/]<name>
npminstall[<@scope>/]<name>@<tag>
npminstall[<@scope>/]<name>@<version>
npminstall[<@scope>/]<name>@<version range>
npminstall<alias>@npm:<name>
npminstall<git-host>:<git-user>/<repo-name>
npminstall<git repo url>
npminstall<tarball file>
npminstall<tarball url>
npminstall<folder>
aliases:npm i,npmadd
common options:[-P|--save-prod|-D|--save-dev|-O|--save-optional][-E|--save-exact][-B|--save-bundle][--no-save][--dry-run]

This command installs a package, and any packages that it depends on. If the package has a package-lock or shrinkwrap file, the installation of dependencies will be driven by that, with annpm-shrinkwrap.json taking precedence if both files exist. Seepackage-lock.json andnpm shrinkwrap.

Apackage is:

a) a folder containing a program described by apackage.json file
b) a gzipped tarball containing (a)
c) a url that resolves to (b)
d) a<name>@<version> that is published on the registry (seeregistry) with (c)
e) a<name>@<tag> (seenpm dist-tag) that points to (d)
f) a<name> that has a "latest" tag satisfying (e)
g) a<git remote url> that resolves to (a)

Even if you never publish your package, you can still get a lot of benefits of using npm if you just want to write a node program (a), and perhaps if you also want to be able to easily install it elsewhere after packing it up into a tarball (b).

npm install (in package directory, no arguments):
Install the dependencies in the local node_modules folder.
In global mode (ie, with-g or--global appended to the command), it installs the current package context (ie, the current working directory) as a global package.
By default,npm install will install all modules listed as dependencies inpackage.json.
With the--production flag (or when theNODE_ENV environment variable is set toproduction), npm will not install modules listed indevDependencies. To install all modules listed in bothdependencies anddevDependencies whenNODE_ENV environment variable is set toproduction, you can use--production=false.
NOTE: The--production flag has no particular meaning when adding a dependency to a project.
npm install <folder>:
Install the package in the directory as a symlink in the current project. Its dependencies will be installed before it's linked. If<folder> sits inside the root of your project, its dependencies may be hoisted to the toplevelnode_modules as they would for other types of dependencies.
npm install <tarball file>:
Install a package that is sitting on the filesystem. Note: if you just want to link a dev directory into your npm root, you can do this more easily by usingnpm link.
Tarball requirements:
- The filenamemust use.tar,.tar.gz, or.tgz as the extension.
- The package contents should reside in a subfolder inside the tarball (usually it is calledpackage/). npm strips one directory layer when installing the package (an equivalent oftar x --strip-components=1 is run).
- The package must contain apackage.json file withname andversion properties.
Example:
npm install ./package.tgz
npm install <tarball url>:
Fetch the tarball url, and then install it. In order to distinguish between this and other options, the argument must start with "http://" or "https://"
Example:
npm installhttps://github.com/indexzero/forever/tarball/v0.5.6
npm install [<@scope>/]<name>:
Do a<name>@<tag> install, where<tag> is the "tag" config. (Seeconfig. The config's default value islatest.)
In most cases, this will install the version of the modules tagged aslatest on the npm registry.
Example:
npm install sax
npm install <alias>@npm:<name>:
Install a package under a custom alias. Allows multiple versions of a same-name package side-by-side, more convenient import names for packages with otherwise long ones and using git forks replacements or forked npm packages as replacements. Aliasing works only on your project and does not rename packages in transitive dependencies. Aliases should follow the naming conventions stated invalidate-npm-package-name.
Examples:
npm install my-react@npm:reactnpm install jquery2@npm:jquery@2npm install jquery3@npm:jquery@3npm install npa@npm:npm-package-arg
npm install saves any specified packages intodependencies by default. Additionally, you can control where and how they get saved with some additional flags:
- -P, --save-prod: Package will appear in yourdependencies. This is the default unless-D or-O are present.
- -D, --save-dev: Package will appear in yourdevDependencies.
- -O, --save-optional: Package will appear in youroptionalDependencies.
- --no-save: Prevents saving todependencies.
When using any of the above options to save dependencies to your package.json, there are two additional, optional flags:
- -E, --save-exact: Saved dependencies will be configured with an exact version rather than using npm's default semver range operator.
- -B, --save-bundle: Saved dependencies will also be added to yourbundleDependencies list.
Further, if you have annpm-shrinkwrap.json orpackage-lock.json then it will be updated as well.
<scope> is optional. The package will be downloaded from the registry associated with the specified scope. If no registry is associated with the given scope the default registry is assumed. Seescope.
Note: if you do not include the @-symbol on your scope name, npm will interpret this as a GitHub repository instead, see below. Scopes names must also be followed by a slash.
Examples:
```
npminstall sax
npminstall githubname/reponame
npminstall @myorg/privatepackage
npminstall node-tap --save-dev
npminstall dtrace-provider --save-optional
npminstall readable-stream --save-exact
npminstall ansi-regex --save-bundle
```
Note: If there is a file or folder named<name> in the current working directory, then it will try to install that, and only try to fetch the package by name if it is not valid.
npm install [<@scope>/]<name>@<tag>:
Install the version of the package that is referenced by the specified tag. If the tag does not exist in the registry data for that package, then this will fail.
Example:
```
npminstall sax@latest
npminstall @myorg/mypackage@latest
```
npm install [<@scope>/]<name>@<version>:
Install the specified version of the package. This will fail if the version has not been published to the registry.
Example:
```
npminstall sax@0.1.1
npminstall @myorg/privatepackage@1.5.0
```
npm install [<@scope>/]<name>@<version range>:
Install a version of the package matching the specified version range. This will follow the same rules for resolving dependencies described inpackage.json.
Note that most version ranges must be put in quotes so that your shell will treat it as a single argument.
Example:
```
npminstall sax@">=0.1.0 <0.2.0"
npminstall @myorg/privatepackage@">=0.1.0 <0.2.0"
```
npm install <git remote url>:
Installs the package from the hosted git provider, cloning it withgit. For a full git remote url, only that URL will be attempted.
```
<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
```
<protocol> is one ofgit,git+ssh,git+http,git+https, orgit+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 the default branch of the repository is used.
If the repository makes use of submodules, those submodules will be cloned as well.
If the package being installed contains aprepare script, itsdependencies anddevDependencies will be installed, and the prepare script will be run, before the package is packaged and installed.
The following git environment variables are recognized by npm and will be added to the environment when running git:
- GIT_ASKPASS
- GIT_EXEC_PATH
- GIT_PROXY_COMMAND
- GIT_SSH
- GIT_SSH_COMMAND
- GIT_SSL_CAINFO
- GIT_SSL_NO_VERIFY
See the git man page for details.
Examples:
```
npminstall git+ssh://git@github.com:npm/cli.git#v1.0.27
npminstall git+ssh://git@github.com:npm/cli#semver:^5.0
npminstall git+https://isaacs@github.com/npm/cli.git
npminstall git://github.com/npm/cli.git#v1.0.27
GIT_SSH_COMMAND='ssh -i ~/.ssh/custom_ident'npminstall git+ssh://git@github.com:npm/cli.git
```
npm install <githubname>/<githubrepo>[#<commit-ish>]:
npm install github:<githubname>/<githubrepo>[#<commit-ish>]:
Install the package athttps://github.com/githubname/githubrepo by attempting to clone it usinggit.
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, thenmaster is used.
As with regular git dependencies,dependencies anddevDependencies will be installed if the package has aprepare script, before the package is done installing.
Examples:
```
npminstall mygithubuser/myproject
npminstall github:mygithubuser/myproject
```
npm install gist:[<githubname>/]<gistID>[#<commit-ish>|#semver:<semver>]:
Install the package athttps://gist.github.com/gistID by attempting to clone it usinggit. The GitHub username associated with the gist is optional and will not be saved inpackage.json.
As with regular git dependencies,dependencies anddevDependencies will be installed if the package has aprepare script, before the package is done installing.
Example:
```
npminstall gist:101a11beef
```
npm install bitbucket:<bitbucketname>/<bitbucketrepo>[#<commit-ish>]:
Install the package athttps://bitbucket.org/bitbucketname/bitbucketrepo by attempting to clone it usinggit.
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, thenmaster is used.
As with regular git dependencies,dependencies anddevDependencies will be installed if the package has aprepare script, before the package is done installing.
Example:
```
npminstall bitbucket:mybitbucketuser/myproject
```
npm install gitlab:<gitlabname>/<gitlabrepo>[#<commit-ish>]:
Install the package athttps://gitlab.com/gitlabname/gitlabrepo by attempting to clone it usinggit.
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, thenmaster is used.
As with regular git dependencies,dependencies anddevDependencies will be installed if the package has aprepare script, before the package is done installing.
Example:
```
npminstall gitlab:mygitlabuser/myproject
npminstall gitlab:myusr/myproj#semver:^5.0
```

You may combine multiple arguments, and even multiple types of arguments. For example:

npminstall sax@">=0.1.0 <0.2.0" bench supervisor

The--tag argument will apply to all of the specified install targets. If a tag with the given name exists, the tagged version is preferred over newer versions.

The--dry-run argument will report in the usual way what the install would have done without actually installing anything.

The--package-lock-only argument will only update thepackage-lock.json, instead of checkingnode_modules and downloading dependencies.

The-f or--force argument will force npm to fetch remote resources even if a local copy exists on disk.

npminstall sax--force

The--no-fund argument will hide the message displayed at the end of each install that acknowledges the number of dependencies looking for funding. Seenpm-fund(1)

The-g or--global argument will cause npm to install the package globally rather than locally. Seefolders.

The--global-style argument will cause npm to install the package into your localnode_modules folder with the same layout it uses with the globalnode_modules folder. Only your direct dependencies will show innode_modules and everything they depend on will be flattened in theirnode_modules folders. This obviously will eliminate some deduping.

The--ignore-scripts argument will cause npm to not execute any scripts defined in the package.json. Seescripts.

The--legacy-bundling argument will cause npm to install the package such that versions of npm prior to 1.4, such as the one included with node 0.8, can install the package. This eliminates all automatic deduping.

The--link argument will cause npm to link global installs into the local space in some cases.

The--no-bin-links argument will prevent npm from creating symlinks for any binaries the package might contain.

The--no-optional argument will prevent optional dependencies from 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 apackage-lock.json file. When running with package-lock's disabled npm will not automatically prune your node modules when installing.

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 onlydevDependencies or only non-devDependencies to be installed regardless of theNODE_ENV.

The--no-audit argument can be used to disable sending of audit reports to the configured registries. Seenpm-audit for details on what is sent.

Seeconfig. Many of the configuration params have some effect on installation, since that's most of what npm does.

Algorithm

To install a package, npm uses the following algorithm:

load the existing node_modules tree from disk
clone the tree
fetch the package.json and assorted metadata andadd it to the clone
walk the clone andadd any missing dependencies
  dependencies will be added as close to thetop as is possible
  without breaking any other modules
compare the original tree with the cloned tree andmake a list of
actions to take to convert one to the other
execute all of the actions, deepest first
  kinds of actions are install, update, remove and move

For thispackage{dep} structure:A{B,C}, B{C}, C{D}, this algorithm produces:

A
+-- B
+-- C
+-- D

That is, the dependency from B to C is satisfied by the fact that A already caused C to be installed at a higher level. D is still installed at the top level because nothing conflicts with it.

ForA{B,C}, B{C,D@1}, C{D@2}, this algorithm produces:

A
+-- B
+-- C
   `-- D@2
+-- D@1

Because B's D@1 will be installed in the top level, C now has to install D@2 privately for itself. This algorithm is deterministic, but different trees may be produced if two dependencies are requested for installation in a different order.

Seefolders for a more detailed description of the specific folder structures that npm creates.

Limitations of npm's Install Algorithm

npm will refuse to install any package with an identical name to the current package. This can be overridden with the--force flag, but in most cases can simply be addressed by changing the local package name.

There are some very rare and pathological edge-cases where a cycle can cause npm to try to install a never-ending tree of packages. Here is the simplest case:

A -> B -> A' -> B' -> A -> B -> A' -> B' -> A ->...

whereA is some version of a package, andA' is a different version of the same package. BecauseB depends on a different version ofA than the one that is already in the tree, it must install a separate copy. The same is true ofA', which must installB'. BecauseB' depends on the original version ofA, which has been overridden, the cycle falls into infinite regress.

To avoid this situation, npm flat-out refuses to install anyname@version that is already present anywhere in the tree of package folder ancestors. A more correct, but more complex, solution would be to symlink the existing version into the new location. If this ever affects a real use-case, it will be investigated.

Movatterモバイル変換

Site navigation

npm-install

Synopsis

Description

Algorithm

Limitations of npm's Install Algorithm

See Also

Table of contents