You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"It is highly recommended you commit the generated package lock to source control: this will allow anyone else on your team, your deployments, your CI/continuous integration, and anyone else who runs npm install in your package source to get the exact same dependency tree that you were developing on."
Also: running npm install without --force results in multiple resolve issues.
The text was updated successfully, but these errors were encountered:
While creating a PR I noticed that the project is missing a lock file.
From https://docs.npmjs.com/cli/v6/configuring-npm/package-locks/#:~:text=It%20is%20highly%20recommended%20you,that%20you%20were%20developing%20on:
"It is highly recommended you commit the generated package lock to source control: this will allow anyone else on your team, your deployments, your CI/continuous integration, and anyone else who runs npm install in your package source to get the exact same dependency tree that you were developing on."
Also: running
npm install
without--force
results in multiple resolve issues.The text was updated successfully, but these errors were encountered: