Repository navigation
file: dependencies cannot resolve a workspace package peer #1677
A The app depends on Aube fails both ways:
Either way The repro is a three-package local workspace with no registry dependencies. I found it with an Expo module in pingdotgg/t3code that is installed as Could aube link a |
Replies: 3 comments
|
Thanks for the clear repro. I reproduced both failures, the dangling link from pnpm's lockfile and the missing link on a fresh install, in isolated and hoisted mode. There were two causes: aube never read a The fix is up in #1679. With it, your One limit: a required peer of a AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable. |
|
Implemented in #1679: fix(install): link workspace peers of file: dependencies |
|
Retested with
PNPM_BIN=/path/to/real/pnpm ./repro.shIt now exits 0 with native pnpm 12.8.1 as the control. The pnpm control, the frozen install from pnpm's lockfile, and the fresh aube install all link I also checked the original case in pingdotgg/t3code: a frozen aube install links the Fix shipped in aube 2.7.0 via #1679. Marking your reply as the answer. |
Thanks for the clear repro. I reproduced both failures, the dangling link from pnpm's lockfile and the missing link on a fresh install, in isolated and hoisted mode. There were two causes: aube never read a
file:package'speerDependencies, and it kept pnpm'slink:snapshot edge as a raw string that points at a virtual-store entry that doesn't exist.The fix is up in #1679. With it, your
repro.shpasses for the pnpm control, the frozen install from pnpm's lockfile, and the fresh install.@x/mdnow resolves@x/sharedto the workspace package.One limit: a required peer of a
file:package that nothing in scope provides is still not auto-installed. That isn't your case, since@x/sharedis a …