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

Added warning about pnpm support for prune #736

Closed
wants to merge 4 commits into from

Conversation

ivoilic
Copy link
Contributor

@ivoilic ivoilic commented Feb 13, 2022

Currently the prune command isn't implemented for pnpm, but the docs don't mention that.

Currently the prune command isn't implemented for pnpm, but the docs don't mention that.
(See this issue: vercel#534)
@vercel
Copy link

vercel bot commented Feb 13, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/vercel/turbo-site/AsaVoX8Dxwy29prwWj58YarisvXA
✅ Preview: https://turbo-site-git-fork-ivoilic-patch-2.vercel.sh

@ivoilic
Copy link
Contributor Author

ivoilic commented Feb 13, 2022

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_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you use <Callout>?

@jlarmstrongiv
Copy link

Is there an issue I can watch for when prune --docker is implemented for npm?

@tknickman
Copy link
Member

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.

@tknickman tknickman closed this Jul 11, 2022
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.

4 participants