Lines Matching full:package
4 description: Install a package
9 ## Install a package
14 npm install (with no args, in package dir)
32 This command installs a package, and any packages that it depends on. If the
33 package has a package-lock or shrinkwrap file, the installation of dependencies
35 files exist. See [package-lock.json](/configuring-npm/package-lock-json) and [`npm shrinkwrap`](/cl…
37 A `package` is:
39 * a) a folder containing a program described by a [`package.json`](/configuring-npm/package-json) f…
47 Even if you never publish your package, you can still get a lot of
53 * `npm install` (in package directory, no arguments):
58 it installs the current package context (ie, the current working
59 directory) as a global package.
62 in [`package.json`](/configuring-npm/package-json).
75 Install the package in the directory as a symlink in the current project.
82 Install a package that is sitting on the filesystem. Note: if you just want
89 …package contents should reside in a subfolder inside the tarball (usually it is called `package/`)…
90 * The package must contain a `package.json` file with `name` and `version` properties.
94 npm install ./package.tgz
119 Install a package under a custom alias. Allows multiple versions of
120 a same-name package side-by-side, more convenient import names for
125 …[`validate-npm-package-name`](https://www.npmjs.com/package/validate-npm-package-name#naming-rules…
132 npm install npa@npm:npm-package-arg
139 * `-P, --save-prod`: Package will appear in your `dependencies`. This is the
142 * `-D, --save-dev`: Package will appear in your `devDependencies`.
144 * `-O, --save-optional`: Package will appear in your `optionalDependencies`.
149 package.json, there are two additional, optional flags:
157 Further, if you have an `npm-shrinkwrap.json` or `package-lock.json` then it
160 `<scope>` is optional. The package will be downloaded from the registry
182 fetch the package by name if it is not valid.
186 Install the version of the package that is referenced by the specified tag.
187 If the tag does not exist in the registry data for that package, then this
199 Install the specified version of the package. This will fail if the
211 Install a version of the package matching the specified version range. This
212 …the same rules for resolving dependencies described in [`package.json`](/configuring-npm/package-j…
225 Installs the package from the hosted git provider, cloning it with `git`.
245 If the package being installed contains a `prepare` script, its
247 script will be run, before the package is packaged and installed.
275 Install the package at `https://github.com/githubname/githubrepo` by
286 be installed if the package has a `prepare` script, before the package is
298 Install the package at `https://gist.github.com/gistID` by attempting to
300 optional and will not be saved in `package.json`.
303 be installed if the package has a `prepare` script, before the package is
314 Install the package at `https://bitbucket.org/bitbucketname/bitbucketrepo`
325 be installed if the package has a `prepare` script, before the package is
336 Install the package at `https://gitlab.com/gitlabname/gitlabrepo`
347 be installed if the package has a `prepare` script, before the package is
371 The `--package-lock-only` argument will only update the `package-lock.json`,
385 The `-g` or `--global` argument will cause npm to install the package globally
388 The `--global-style` argument will cause npm to install the package into
395 scripts defined in the package.json. See [`scripts`](/using-npm/scripts).
397 The `--legacy-bundling` argument will cause npm to install the package such
399 can install the package. This eliminates all automatic deduping.
405 any binaries the package might contain.
411 package lock or shrinkwrap file and use the package.json instead.
413 The `--no-package-lock` argument will prevent npm from creating a
414 `package-lock.json` file. When running with package-lock's disabled npm
431 To install a package, npm uses the following algorithm:
435 fetch the package.json and assorted metadata and add it to the clone
445 For this `package{dep}` structure: `A{B,C}, B{C}, C{D}`,
478 npm will refuse to install any package with an identical name to the
479 current package. This can be overridden with the `--force` flag, but in
480 most cases can simply be addressed by changing the local package name.
490 where `A` is some version of a package, and `A'` is a different version
491 of the same package. Because `B` depends on a different version of `A`
498 `name@version` that is already present anywhere in the tree of package
519 * [package.json](/configuring-npm/package-json)