Skip to content
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
mary-ext opened this issue Apr 19, 2024 · 2 comments · Fixed by #7999
Closed
2 of 4 tasks

Upgrading packages doesn't work when an aliased workspace dependency is present #7975

mary-ext opened this issue Apr 19, 2024 · 2 comments · Fixed by #7999

Comments

@mary-ext
Copy link

mary-ext commented Apr 19, 2024

Verify latest release

  • I verified that the issue exists in the latest pnpm 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

  1. Run pnpm up -r on the workspace root

Describe the Bug

pnpm complains that it can't find package c on the workspace, even though c is set to alias package b

Scope: all 3 workspace projects
/pnpm-workspace-alias/a:
 ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In a: "c@workspace:*" is in the dependencies but no package named "c" is present in the workspace

This error happened while installing a direct dependency of /pnpm-workspace-alias/a

Packages found in the workspace: a, b

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?

  • macOS
  • Windows
  • Linux

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)

@mary-ext
Copy link
Author

mary-ext commented Apr 19, 2024

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.

@KSXGitHub

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants