-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
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
bring back --only=dev
and --only=prod
for npm v7
#2028
Comments
From #1969 (comment)
|
from #1969 (comment)
|
--only=dev
for npm v7--only=dev
and --only=prod
for npm v7
Note: if Updated Also, since we still have to resolve dev deps for the purpose of building the ideal tree/shrinkwrap, even if they're not being installed, it may be that the "don't fetch devDep manifests in |
If only this is the case(about won't fix), does it mean that if I want to achieve such an effect, I can only delete the corresponding node in |
I have been tracking this issue for many years. If this is the final result (no need to fix), for the npm community, I don't know what to say. this issue exists since |
Ability to install only dev-dependencies, or only production-dependencies, would be great. What would be even better, is if we could make arbitrary groups in the package.json file, and only install one or several groups. A few group examples would be 'production', 'development', 'linting', 'continuous-integration', … A good use-case for this is to have a linting group that's only installed during certain CI-runs. On the tree (in package-lock.json, you could have e.g. |
npm v7 always installs production deps. There's no way to omit them. We should bring this back, and let you do
--omit=prod
as well.The text was updated successfully, but these errors were encountered: