Replies: 1 comment
-
|
This would be useful. As a workaround, here are some current options: 1. Reinstall specific package # Remove and reinstall
pnpm remove some-package && pnpm add some-package2. Prune store + reinstall rm -rf node_modules
pnpm store prune
pnpm install3. Verify via checksums (manual) # Get expected hash from lockfile
grep -A5 "package-name" pnpm-lock.yaml | grep integrity
# Compare with actual
sha512sum node_modules/.pnpm/package-name@version/node_modules/package-name/file.js4. Use pnpm install --forceThis should relink everything from store, though it won't fix store corruption. Feature request idea: # Verify integrity of all installed packages
pnpm verify
# Verify and fix mismatches
pnpm verify --fix
# Verify specific package
pnpm verify lodashThis could compare actual file hashes against lockfile integrity, report mismatches, and optionally re-extract from store or redownload. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, it would be great if there was a way to verify contents of the packages in the node_modules (and store?).
Scenario: I accidentally changed a file when i was exploring source code of a dependency. I use pnpm workspaces. Currently there's no easy way to fix this cause:
Idea: add a command to verify or reinstall contents of node_modules (and store?). It can be based on checksum
Beta Was this translation helpful? Give feedback.
All reactions