We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I verified that the issue exists in the latest pnpm release
8.14.1
No response
https://github.com/RuudBurger/pnpm-patch-problem
pnpm install
packages/package1
packages/package2
pnpm dlx del-cli "**/node_modules"; pnpm i
package1
package2
pnpm dlx del-cli "**/node_modules"; pnpm store prune; pnpm i
Extra:
rm -Rf packages/package2/node_modules; pnpm i
See above. The setting node-linker=hoisted is key here. Our repo used react-native and it doesn't work well without the hoisted method.
node-linker=hoisted
Patching file should be consistent, but after store prune it patches the filed differently.
This means that a CI with no cache, behaves differently then a local dev environment that never did a pnpm store prune.
pnpm store prune
18.18.2
macOS
The text was updated successfully, but these errors were encountered:
await-ovo
Successfully merging a pull request may close this issue.
Verify latest release
I verified that the issue exists in the latest pnpm release
pnpm version
8.14.1
Which area(s) of pnpm are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue or a replay of the bug
https://github.com/RuudBurger/pnpm-patch-problem
Reproduction steps
pnpm install
packages/package1
has the patch applied,packages/package2
doesn'tpnpm dlx del-cli "**/node_modules"; pnpm i
package1
andpackage2
have the patch appliedpnpm dlx del-cli "**/node_modules"; pnpm store prune; pnpm i
Extra:
rm -Rf packages/package2/node_modules; pnpm i
package1
has the patch applied twicepackage2
has the patched applied also, minus 1. So it uses the already patched package as a basis, and re-applies the patch after it copies it.Describe the Bug
See above. The setting
node-linker=hoisted
is key here. Our repo used react-native and it doesn't work well without the hoisted method.Expected Behavior
Patching file should be consistent, but after store prune it patches the filed differently.
This means that a CI with no cache, behaves differently then a local dev environment that never did a
pnpm store prune
.Which Node.js version are you using?
18.18.2
Which operating systems have you used?
macOS
If your OS is a Linux based, which one it is? (Include the version if relevant)
No response
The text was updated successfully, but these errors were encountered: