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
It should obey that flag. I know that i can do "npm i --no-optional", but that defeats the whole purpose of having lock files.
The text was updated successfully, but these errors were encountered:
Whether npm ci --no-optional works appears to depend on one ore more additional factors. It appears to work in my environment which is:
npm ci --no-optional
Sorry, something went wrong.
Why is this closed? What about linux users?
No branches or pull requests
It should obey that flag. I know that i can do "npm i --no-optional", but that defeats the whole purpose of having lock files.
The text was updated successfully, but these errors were encountered: