Reputation: 7902
From the npm 5 doc:
The --no-package-lock argument will prevent npm from creating a package-lock.json file.
Does an npm install
with --no-package-lock
follows the package-lock.json
(if already exists) deterministic install / nested locked versions ? Or does it completly ignore it ?
Upvotes: 18
Views: 11432
Reputation: 9189
For deterministic install you must have an package-lock.json
and use npm ci
. See https://docs.npmjs.com/cli/v7/commands/npm-ci
This command is similar to 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.
Upvotes: 0
Reputation: 7902
Answer from the @npm_support:
Using
--no-package-lock
skips the package-lock. It is neither read nor written as if the package-lock feature did not exist.
So the package-lock.json
file isn't used at all when the --no-package-lock
is on.
Upvotes: 24