We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
caused by #232
current implementation tells users to have a package lock file. internally it is not really needed. instead, npm ls is utilized.
npm ls
and sometimes it is just not there - see https://docs.npmjs.com/cli/v9/using-npm/config#package-lock
remove the demand for a package lock file.
see npm config for the topic: https://docs.npmjs.com/cli/v9/using-npm/config#package-lock
The text was updated successfully, but these errors were encountered:
originally the pinning on the lockfile was enforced for forward-compatibility, in case in the future the lockfile needed to be read manually.
this is no longer planned, nor foreseen. therefore, the lock-file requirement can be dropped.
Sorry, something went wrong.
jkowalleck
Successfully merging a pull request may close this issue.
caused by #232
Is your feature request related to a problem? Please describe.
current implementation tells users to have a package lock file.
internally it is not really needed. instead,
npm ls
is utilized.and sometimes it is just not there - see https://docs.npmjs.com/cli/v9/using-npm/config#package-lock
Describe the solution you'd like
remove the demand for a package lock file.
Additional context
see npm config for the topic: https://docs.npmjs.com/cli/v9/using-npm/config#package-lock
The text was updated successfully, but these errors were encountered: