-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Added warning about pnpm support for prune #736
Conversation
Currently the prune command isn't implemented for pnpm, but the docs don't mention that. (See this issue: vercel#534)
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/vercel/turbo-site/AsaVoX8Dxwy29prwWj58YarisvXA |
This other PR should probably be merged first 😉 |
@@ -326,6 +326,8 @@ This command will generate folder called `out` with the following inside of it: | |||
- A new pruned lockfile that only contains the pruned subset of the original root lockfile with the dependencies that are actually used by the packages in the pruned workspace. | |||
- A copy of the root `package.json` | |||
|
|||
⚠️ _This command is not yet implemented for pnpm and npm_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use <Callout>
?
Is there an issue I can watch for when |
Closing this one in favor of #1505. We had a few more issues about this so wanted to get it in quickly! Thanks for raising this. |
Currently the prune command isn't implemented for pnpm, but the docs don't mention that.