Lines Matching full:package
3 \fBnpm-install\fR \- Install a package
8 npm install (with no args, in package dir)
26 This command installs a package, and any packages that it depends on\. If the
27 package has a package\-lock or shrinkwrap file, the installation of dependencies
29 files exist\. See npm help package\-lock\.json and npm help \fBshrinkwrap\fP\|\.
31 A \fBpackage\fP is:
34 a) a folder containing a program described by a npm help \fBpackage\.json\fP file
50 Even if you never publish your package, you can still get a lot of
56 \fBnpm install\fP (in package directory, no arguments):
59 it installs the current package context (ie, the current working
60 directory) as a global package\.
62 in npm help \fBpackage\.json\fP\|\.
75 Install the package in the directory as a symlink in the current project\.
81 Install a package that is sitting on the filesystem\. Note: if you just want
90 …package contents should reside in a subfolder inside the tarball (usually it is called \fBpackage/…
92 The package must contain a \fBpackage\.json\fP file with \fBname\fP and \fBversion\fP properties\.
97 npm install \./package\.tgz
128 Install a package under a custom alias\. Allows multiple versions of
129 a same\-name package side\-by\-side, more convenient import names for
134 …\fBvalidate\-npm\-package\-name\fP \fIhttps://www\.npmjs\.com/package/validate\-npm\-package\-name…
142 npm install npa@npm:npm\-package\-arg
154 * `\-P, \-\-save\-prod`: Package will appear in your `dependencies`\. This is the
157 * `\-D, \-\-save\-dev`: Package will appear in your `devDependencies`\.
159 * `\-O, \-\-save\-optional`: Package will appear in your `optionalDependencies`\.
164 package\.json, there are two additional, optional flags:
172 Further, if you have an `npm\-shrinkwrap\.json` or `package\-lock\.json` then it
175 `<scope>` is optional\. The package will be downloaded from the registry
197 fetch the package by name if it is not valid\.
203 Install the version of the package that is referenced by the specified tag\.
204 If the tag does not exist in the registry data for that package, then this
216 Install the specified version of the package\. This will fail if the
228 Install a version of the package matching the specified version range\. This
229 …will follow the same rules for resolving dependencies described in npm help \fBpackage\.json\fP\|\.
242 Installs the package from the hosted git provider, cloning it with \fBgit\fP\|\.
260 If the package being installed contains a \fBprepare\fP script, its
262 script will be run, before the package is packaged and installed\.
298 Install the package at \fBhttps://github\.com/githubname/githubrepo\fP by
307 be installed if the package has a \fBprepare\fP script, before the package is
319 Install the package at \fBhttps://gist\.github\.com/gistID\fP by attempting to
321 optional and will not be saved in \fBpackage\.json\fP\|\.
323 be installed if the package has a \fBprepare\fP script, before the package is
334 Install the package at \fBhttps://bitbucket\.org/bitbucketname/bitbucketrepo\fP
343 be installed if the package has a \fBprepare\fP script, before the package is
354 Install the package at \fBhttps://gitlab\.com/gitlabname/gitlabrepo\fP
363 be installed if the package has a \fBprepare\fP script, before the package is
392 The \fB\-\-package\-lock\-only\fP argument will only update the \fBpackage\-lock\.json\fP,
408 The \fB\-g\fP or \fB\-\-global\fP argument will cause npm to install the package globally
411 The \fB\-\-global\-style\fP argument will cause npm to install the package into
418 scripts defined in the package\.json\. See npm help \fBscripts\fP\|\.
420 The \fB\-\-legacy\-bundling\fP argument will cause npm to install the package such
422 can install the package\. This eliminates all automatic deduping\.
428 any binaries the package might contain\.
434 package lock or shrinkwrap file and use the package\.json instead\.
436 The \fB\-\-no\-package\-lock\fP argument will prevent npm from creating a
437 \fBpackage\-lock\.json\fP file\. When running with package\-lock's disabled npm
453 To install a package, npm uses the following algorithm:
459 fetch the package\.json and assorted metadata and add it to the clone
470 For this \fBpackage{dep}\fP structure: \fBA{B,C}, B{C}, C{D}\fP,
506 npm will refuse to install any package with an identical name to the
507 current package\. This can be overridden with the \fB\-\-force\fP flag, but in
508 most cases can simply be addressed by changing the local package name\.
520 where \fBA\fP is some version of a package, and \fBA'\fP is a different version
521 of the same package\. Because \fBB\fP depends on a different version of \fBA\fP
528 \fBname@version\fP that is already present anywhere in the tree of package
563 npm help package\.json