mirror of
https://github.com/titanscouting/tra-analysis.git
synced 2025-10-24 01:49:20 +00:00
push all website files
This commit is contained in:
53
website/node_modules/npm/doc/cli/npm-uninstall.md
generated
vendored
Normal file
53
website/node_modules/npm/doc/cli/npm-uninstall.md
generated
vendored
Normal file
@@ -0,0 +1,53 @@
|
||||
npm-uninstall(1) -- Remove a package
|
||||
=============================
|
||||
|
||||
## SYNOPSIS
|
||||
|
||||
npm uninstall [<@scope>/]<pkg>[@<version>]... [-S|--save|-D|--save-dev|-O|--save-optional|--no-save]
|
||||
|
||||
aliases: remove, rm, r, un, unlink
|
||||
|
||||
## DESCRIPTION
|
||||
|
||||
This uninstalls a package, completely removing everything npm installed
|
||||
on its behalf.
|
||||
|
||||
Example:
|
||||
|
||||
npm uninstall sax
|
||||
|
||||
In global mode (ie, with `-g` or `--global` appended to the command),
|
||||
it uninstalls the current package context as a global package.
|
||||
|
||||
`npm uninstall` takes 3 exclusive, optional flags which save or update
|
||||
the package version in your main package.json:
|
||||
|
||||
* `-S, --save`: Package will be removed from your `dependencies`.
|
||||
|
||||
* `-D, --save-dev`: Package will be removed from your `devDependencies`.
|
||||
|
||||
* `-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.
|
||||
|
||||
Scope is optional and follows the usual rules for `npm-scope(7)`.
|
||||
|
||||
Examples:
|
||||
|
||||
npm uninstall sax --save
|
||||
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)
|
||||
* npm-install(1)
|
||||
* npm-folders(5)
|
||||
* npm-config(1)
|
||||
* npm-config(7)
|
||||
* npmrc(5)
|
||||
Reference in New Issue
Block a user