fix(docs): re-add --save and explanation of when it is useful

Author: wraithgar

docs/content/commands/npm-uninstall.md

@@ -7,7 +7,7 @@ description: Remove a package
 ### Synopsis
 
 ```bash
-npm uninstall [<@scope>/]<pkg>[@<version>]... [--no-save]
+npm uninstall [<@scope>/]<pkg>[@<version>]... [--save|--no-save]
 
 aliases: remove, rm, r, un, unlink
 ```
@@ -24,9 +24,13 @@ It also removes the package from the `dependencies`, `devDependencies`,
 Futher, if you have an `npm-shrinkwrap.json` or `package-lock.json`, npm
 will update those files as well.
 
-`npm uninstall` takes one optional flag, `--no-save` which will tell npm
-not to remove the package from your `package.json`,
-`npm-shrinkwrap.json`, or `package-lock.json` files
+`--no-save` will tell npm not to remove the package from your
+`package.json`, `npm-shrinkwrap.json`, or `package-lock.json` files.
+
+`--save` will tell npm to remove the package from your `package.json`,
+`npm-shrinkwrap.json`, and `package-lock.json` files.  This is the
+default, but you may need to use this if you have for instance
+`save=false` in your `npmrc` file
 
 In global mode (ie, with `-g` or `--global` appended to the command),
 it uninstalls the current package context as a global package.

lib/uninstall.js

@@ -9,7 +9,7 @@ const completion = require('./utils/completion/installed-shallow.js')
 
 const usage = usageUtil(
   'uninstall',
-  'npm uninstall [<@scope>/]<pkg>[@<version>]... [--no-save]'
+  'npm uninstall [<@scope>/]<pkg>[@<version>]... [--save, --no-save]'
 )
 
 const cmd = (args, cb) => rm(args).then(() => cb()).catch(cb)