Skip to content
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

docs: update npm-prune description #6985

Merged
merged 1 commit into from
Nov 13, 2023
Merged

docs: update npm-prune description #6985

merged 1 commit into from
Nov 13, 2023

Conversation

Eomm
Copy link
Contributor

@Eomm Eomm commented Nov 13, 2023

The documentation uses a deprecated --production flag.
Using it shows the following warning:

$ npm prune --production
npm WARN config production Use `--omit=dev` instead.

The --production flag is not documented as well:

image

References

Relates to:

This PR makes clear that --production should not be used anymore.

@Eomm Eomm requested a review from a team as a code owner November 13, 2023 13:34
@wraithgar
Copy link
Member

Is there a reason this is on the v9 branch?

@Eomm
Copy link
Contributor Author

Eomm commented Nov 13, 2023

I was using Node.js 18
Should I target latest and then it will be back-ported?

Did not found any guidance about this topic in https://github.com/npm/cli/blob/latest/CONTRIBUTING.md

@wraithgar
Copy link
Member

We're still working out our official backporting policy, sorry. For now you should target latest and then once it's accepted you can make a second PR for the backport.

@wraithgar wraithgar merged commit 6ab06d7 into npm:release/v9 Nov 13, 2023
8 checks passed
@wraithgar
Copy link
Member

Thanks for both!

@github-actions github-actions bot mentioned this pull request Nov 13, 2023
@Eomm Eomm deleted the patch-1 branch November 13, 2023 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants