Add or remove the ability of users and teams to have read-only or read-write access to a package.

* You have been given read-write privileges for a package, either as a member of a team or directly as an owner.

If vulnerabilities were found the exit code will depend on the [`audit-level` config](/using-npm/config#audit-level).

This command is similar to [`npm install`](/commands/npm-install), except it's meant to be used in automated environments such as test platforms, continuous integration, and deployment -- or any situation where you want to make sure you're doing a clean install of your dependencies.

* `npm ci` can only install entire projects at a time: individual dependencies cannot be added with this command.

* If a `node_modules` is already present, it will be automatically removed before `npm ci` begins its install.

NOTE: If you create your `package-lock.json` file by running `npm install` with flags that can affect the shape of your dependency tree, such as

Use `--json` to show the settings in json format.

Though `d`'s dependency on `c@1.x` could have been satisfied by `c@1.0.3`, the newer `c@1.9.0` dependency was used, because npm favors updates by default, even when doing so causes duplication.

SemVer ranges passed to this command are interpreted such that they *do* include prerelease versions.

To un-deprecate a package, specify an empty string (`""`) for the `message` argument.

This command tries to guess at the likely location of a package's documentation URL, and then tries to open it using the [`--browser` config](/using-npm/config#browser) param.

+ The primary npm registry, `registry.npmjs.com`, or another service that uses the registry API, is available.

+ The directories that npm uses, `node_modules` (both locally and globally), exist and can be written by the current user.

Many issues are often attributable to things that are outside npm's code base, so `npm doctor` confirms that the npm installation is in a good state.

If this check fails, you may be using a proxy that needs to be configured, or may need to talk to your IT staff to get access over HTTPS to `registry.npmjs.org`.

This check is done against whichever registry you've configured (you can see what that is by running `npm config get registry`), and if you're using a private registry that doesn't support the `/whoami` endpoint supported by the primary registry, this check may fail.

Those of you who want access to new ECMAscript features or bleeding-edge changes to Node's standard library may be running a newer version, and some may be required to run an older version of Node because of enterprise change control policies.

While it's documented in the README, it may not be obvious that npm needs Git installed to do many of the things that it does.

Also, in some cases – especially on Windows – you may have Git set up in such a way that it's not accessible via your `PATH` so that npm can find it.

* Your local `node_modules` path, if you're running `npm doctor` with a project directory, must be readable and writable by the user running npm.

Selects a dependency in the current project and opens the package folder in the default editor (or whatever you've configured as the npm `editor` config -- see [`npm-config`](npm-config).)

If a package name is provided then it tries to open its funding url using the [`--browser` config](/using-npm/config#browser) param; if there are multiple funding sources for the package, the user will be instructed to pass the

It's possible to filter the results to only include a single workspace and its dependencies using the [`workspace` config](/using-npm/config#workspace) option.