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.

Sign up for GitHub

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

Jump to bottom

fix(prune): should work in a workspace #4691

Merged
merged 1 commit into from May 7, 2022
Merged

fix(prune): should work in a workspace #4691

merged 1 commit into from May 7, 2022

Conversation

zkochan
Copy link
Member

@zkochan zkochan commented May 6, 2022

close #4647

@zkochan zkochan merged commit 0075fcd into main May 7, 2022
@zkochan zkochan deleted the fix/4647 branch May 7, 2022 01:10
zkochan added a commit that referenced this pull request May 7, 2022
@zkochan
fix(prune): should work in a workspace (#4691)
2012684 
close #4647
This was referenced May 8, 2022
Closed
Closed
@humphd
Copy link

humphd commented Jan 22, 2024

Based on this fix, is the warning in the docs still correct, or outdated?

WARNING
The prune command does not support recursive execution on a monorepo currently. To only install production-dependencies in a monorepo node_modules folders can be deleted and then re-installed with pnpm install --prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[pnpm v7] pnpm prune: ERR_PNPM_NO_MATCHING_VERSION_INSIDE_WORKSPACE
2 participants
@zkochan @humphd