Repository navigation
[Bug?]: yarn fails to symlink in-range workspace dependency #7260
Description
Self-service
- I'd be willing to implement a fix
Describe the bug
Project A depends on B@^5.0.0.
Project B is at 5.2.0.
5.2.0 satisfies the range ^5.0.0, however Yarn does not link B into node_modules of A.
Workaround
To fix the issue, A's dependency has to be changed to B@^5.2.0, defeating the purpose of using a range.
To reproduce
TODO. Let me know if this is expected or seems like a bug. I'll make a repro.
Environment
System:
OS: macOS 26.5
CPU: (8) arm64 Apple M2
Binaries:
Node: 26.7.0 - /private/var/folders/7y/wy4mhdj114g5xj1ktvh6hdz80000gn/T/xfs-0176e10c/node
Yarn: 4.18.0 - /private/var/folders/7y/wy4mhdj114g5xj1ktvh6hdz80000gn/T/xfs-0176e10c/yarn
npm: 12.0.2 - /Users/trusktr/.npm-global/bin/npm
pnpm: 10.24.0 - /Users/trusktr/.npm-global/bin/pnpm
Deno: 1.38.3 - /opt/homebrew/bin/denoAdditional context
No response
Activity
clemyan commentedon Aug 21, 2026
By "Project A" and "Project B", do you mean two workspaces of the same project?
Two possibilities come to mind:
node_modulesabove the dependent workspaceenableTransparentWorkspacesisfalse, then a semver range will not resolve to a workspace and fall back to fetching from npmNot sure if I'm missing something, but if it is neither then it does sound like a bug