Lines Matching full:install
2 title: npm-install
4 description: Install a package
10 npm install [<package-spec> ...]
44 you also want to be able to easily install it elsewhere after packing it up
48 * `npm install` (in a package directory, no arguments):
50 Install the dependencies to the local `node_modules` folder.
56 By default, `npm install` will install all modules listed as
60 variable is set to `production`), npm will not install modules listed
61 in `devDependencies`. To install all modules listed in both
68 * `npm install <folder>`:
73 *npm will not install the package dependencies* in the directory `<folder>`,
76 …u want to install the content of a directory like a package from the registry instead of creating …
81 npm install ../../other-package --install-links
82 npm install ./sub-package
85 * `npm install <tarball file>`:
87 Install a package that is sitting on the filesystem. Note: if you just
104 npm install ./package.tgz
107 * `npm install <tarball url>`:
109 Fetch the tarball url, and then install it. In order to distinguish between
115 npm install https://github.com/indexzero/forever/tarball/v0.5.6
118 * `npm install [<@scope>/]<name>`:
120 Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
123 In most cases, this will install the version of the modules tagged as
129 npm install sax
132 `npm install` saves any specified packages into `dependencies` by default.
170 npm install sax
171 npm install githubname/reponame
172 npm install @myorg/privatepackage
173 npm install node-tap --save-dev
174 npm install dtrace-provider --save-optional
175 npm install readable-stream --save-exact
176 npm install ansi-regex --save-bundle
180 working directory, then it will try to install that, and only try to
183 * `npm install <alias>@npm:<name>`:
185 Install a package under a custom alias. Allows multiple versions of
196 npm install my-react@npm:react
197 npm install jquery2@npm:jquery@2
198 npm install jquery3@npm:jquery@3
199 npm install npa@npm:npm-package-arg
202 * `npm install [<@scope>/]<name>@<tag>`:
204 Install the version of the package that is referenced by the specified tag.
211 npm install sax@latest
212 npm install @myorg/mypackage@latest
215 * `npm install [<@scope>/]<name>@<version>`:
217 Install the specified version of the package. This will fail if the
223 npm install sax@0.1.1
224 npm install @myorg/privatepackage@1.5.0
227 * `npm install [<@scope>/]<name>@<version range>`:
229 Install a version of the package matching the specified version range.
239 npm install sax@">=0.1.0 <0.2.0"
240 npm install @myorg/privatepackage@"16 - 17"
243 * `npm install <git remote url>`:
286 npm install git+ssh://git@github.com:npm/cli.git#v1.0.27
287 npm install git+ssh://git@github.com:npm/cli#pull/273
288 npm install git+ssh://git@github.com:npm/cli#semver:^5.0
289 npm install git+https://isaacs@github.com/npm/cli.git
290 npm install git://github.com/npm/cli.git#v1.0.27
291 GIT_SSH_COMMAND='ssh -i ~/.ssh/custom_ident' npm install git+ssh://git@github.com:npm/cli.git
294 * `npm install <githubname>/<githubrepo>[#<commit-ish>]`:
295 * `npm install github:<githubname>/<githubrepo>[#<commit-ish>]`:
297 Install the package at `https://github.com/githubname/githubrepo` by
314 npm install mygithubuser/myproject
315 npm install github:mygithubuser/myproject
318 * `npm install gist:[<githubname>/]<gistID>[#<commit-ish>|#semver:<semver>]`:
320 Install the package at `https://gist.github.com/gistID` by attempting to
331 npm install gist:101a11beef
334 * `npm install bitbucket:<bitbucketname>/<bitbucketrepo>[#<commit-ish>]`:
336 Install the package at `https://bitbucket.org/bitbucketname/bitbucketrepo`
353 npm install bitbucket:mybitbucketuser/myproject
356 * `npm install gitlab:<gitlabname>/<gitlabrepo>[#<commit-ish>]`:
358 Install the package at `https://gitlab.com/gitlabname/gitlabrepo`
375 npm install gitlab:mygitlabuser/myproject
376 npm install gitlab:myusr/myproj#semver:^5.0
383 npm install sax@">=0.1.0 <0.2.0" bench supervisor
386 The `--tag` argument will apply to all of the specified install targets. If
390 The `--dry-run` argument will report in the usual way what the install
401 npm install sax --force
452 #### `install-strategy`
458 (default): Install non-duplicated in top-level, and duplicated as necessary
459 within directory structure. nested: (formerly --legacy-bundling) install in
460 place, no hoisting. shallow (formerly --global-style) only install direct
461 deps at top-level. linked: (experimental) install in node_modules/.store,
471 `--install-strategy=nested`
473 Instead of hoisting package installs in `node_modules`, install packages in
476 de-duplicating. Sets `--install-strategy=nested`.
485 `--install-strategy=shallow`
487 Only install direct dependencies in the top level `node_modules`, but hoist
488 on deeper dependencies. Sets `--install-strategy=shallow`.
517 Option that allows for defining which types of dependencies to install.
532 conflicting `peerDependencies` will be treated as an install failure, even
589 Run all build scripts (ie, `preinstall`, `install`, and `postinstall`)
643 When "true" displays the message at the end of each `npm install`
656 commands that modify your local installation, eg, `install`, `update`,
669 Override CPU architecture of native modules to install. Acceptable values
679 Override OS of native modules to install. Acceptable values are same as `os`
689 Override libc of native modules to install. Acceptable values are same as
724 Explicitly setting this to false will cause commands like `install` to
727 - Commands that operate on the `node_modules` tree (install, update, etc.)
747 #### `install-links`
761 the npm install algorithm produces:
784 Because B's D@1 will be installed in the top-level, C now has to install