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
When I write a different name (from dependency's own package.json) in dependencies field, I expect that name to be importable.
package.json
dependencies
dependant/package.json
{ "name": "dependant", "private": true, "version": "0.0.0", "dependencies": { "new-name": "file:../dependency" } }
dependency/package.json
{ "name": "old-name", "private": true, "version": "0.0.0" }
pnpm recursive link
pnpm creates a symlink at dependant/node_modules/new-name.
dependant/node_modules/new-name
pnpm creates dependant/node_modules/old-name instead.
dependant/node_modules/old-name
new-name
old-name
dependant
The text was updated successfully, but these errors were encountered:
pnpm link
93375cb
🚢 2.15.2
Sorry, something went wrong.
Wait, why is pnpm still 2.15.1 in npmjs.com?
Nevermind, pnpm@next
yep, we don't make new versions latest immediately. If you need updates earlier, install with the next or rc tag
latest
next
rc
zkochan
No branches or pull requests
TL;DR
When I write a different name (from dependency's own
package.json
) independencies
field, I expect that name to be importable.Steps to reproduce
1. Create a monorepo structure
1.1. File
dependant/package.json
1.2. File
dependency/package.json
2. Link them together
Expected behavior
pnpm creates a symlink at
dependant/node_modules/new-name
.Actual behavior
pnpm creates
dependant/node_modules/old-name
instead.Notes
new-name
but alsoold-name
anddependant
, however, I don't thinkold-name
anddependant
should be created at all. imageThe text was updated successfully, but these errors were encountered: