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
Upgrading packages doesn't work when an aliased workspace dependency is present #7975
Closed
2 of 4 tasks
Labels
Comments
Package installation works fine, so I assumed this was a supported feature. Needed this because I'm publishing some workspace packages but wanted a shorter package name that can be imported by private packages. |
This comment was marked as off-topic.
This comment was marked as off-topic.
KSXGitHub
added a commit
that referenced
this issue
Apr 23, 2024
4 tasks
zkochan
pushed a commit
that referenced
this issue
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Verify latest release
pnpm version
9.0.4
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/mary-ext/repro-pnpm-workspace-alias
Reproduction steps
pnpm up -r
on the workspace rootDescribe the Bug
pnpm complains that it can't find package
c
on the workspace, even thoughc
is set to alias packageb
Expected Behavior
It should be able to run the upgrade
Which Node.js version are you using?
v21.7.2
Which operating systems have you used?
If your OS is a Linux based, which one it is? (Include the version if relevant)
Arch Linux (6.8.7-zen1-1.1-zen)
The text was updated successfully, but these errors were encountered: