Zoltan KochanandClaude Opus 5.5
c13953b3bc
Code blocks that hold only shell commands now use the `sh` language, and blocks showing a file's contents carry a `title` naming the file, across the pnpm v12, pnpm v11, and pnpr docs. Bold file-name labels above code blocks are folded into the titles. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
id, title
| id | title |
|---|---|
| uninstall | Uninstalling pnpm |
Removing the globally installed packages
Before removing the pnpm CLI, it might make sense to remove all global packages that were installed by pnpm.
To list all the global packages, run pnpm ls -g. There are two ways to remove the global packages:
- Run
pnpm rm -g <pkg>...with each global package listed. - Run
pnpm root -gto find the location of the global directory and remove it manually.
Removing the pnpm CLI
If you used the standalone script to install pnpm, then you should be able to uninstall the pnpm CLI by removing the pnpm home directory:
rm -rf "$PNPM_HOME"
You might also want to clean the PNPM_HOME env variable in your shell configuration file ($HOME/.bashrc, $HOME/.zshrc or $HOME/.config/fish/config.fish).
If you used npm to install pnpm, then you should use npm to uninstall pnpm:
npm rm -g pnpm
Removing the global content-addressable store
rm -rf "$(pnpm store path)"
If you used pnpm in non-primary disks, then you must run the above command in every disk, where pnpm was used. pnpm creates one store per disk.