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
About Pnpm link #4439
Comments
You probably need to run Alternatively, you may run in the directory of the B project:
|
It was resolved after I deleted the folder C:\Users\QiYuei\AppData\Roaming\npm\pnpm-global |
@zkochan this can be closed i readed it and the user sayed it is solved just wanted to ping you to clean up issues. |
I find that I often need to delete this folder when I restart or re-pnpm link --global, but it always fails to link without deleting it. Is there something wrong with my operation? @zkochan delete the folder C:\Users\QiYuei\AppData\Roaming\npm\pnpm-global |
I have experienced this same confusing Side note: I'm pretty sure I know by now how npm-link is supposed to work and that I have a healthy expectation of how pnpm-link is supposed to work - but I find the pnpm-link documentation page to still be quite confusing. |
pnpm version: 6.23.1
Code to reproduce the issue:
When I develop A package called A with PNPM, there is an NPM project B that depends on this A. When I debug this A in project B, I used to just to
npm link
in PROJECT A and thennpm link
B in project B. I see that link directives are also in the PNPM documentation, so I try to usepnpm link --global -C
in Project A and thenpnpm link --global A
in project B and find that nodemodules in project B do not have Link AExpected behavior: B link A
Actual behavior:
A call pnpm link --global -C
B call pnpm link --global A
Additional information:
node -v
prints:14.16.1The text was updated successfully, but these errors were encountered: