Yarn PnP users still report intent list not finding skills even after #121, #122, and #124. See discussion: #119
The "Yarn PnP is not yet supported" hard block is already gone, but the real-world path is still broken — likely because the existing PnP tests use synthetic hand-written .pnp.cjs fixtures that don't exercise what real Yarn Berry projects hit.
Scope:
- Reproduce the real Yarn Berry PnP case first (
nodeLinker: pnp, real .pnp.cjs), including the npx @tanstack/intent invocation from the discussion — where Intent runs outside the project's PnP dependency graph.
- Fix discovery for pure PnP, PnP alongside stale
node_modules, and PnP workspaces.
- Make a failed PnP load fail closed with a clear diagnostic instead of silently falling back to importing package code.
Independent of the allowlist work — can land on its own if needed.
Done when: the PnP reproduction (including the npx path) passes in CI, and a broken PnP setup fails with a clear error.
Yarn PnP users still report
intent listnot finding skills even after #121, #122, and #124. See discussion: #119The "Yarn PnP is not yet supported" hard block is already gone, but the real-world path is still broken — likely because the existing PnP tests use synthetic hand-written
.pnp.cjsfixtures that don't exercise what real Yarn Berry projects hit.Scope:
nodeLinker: pnp, real.pnp.cjs), including thenpx @tanstack/intentinvocation from the discussion — where Intent runs outside the project's PnP dependency graph.node_modules, and PnP workspaces.Independent of the allowlist work — can land on its own if needed.
Done when: the PnP reproduction (including the
npxpath) passes in CI, and a broken PnP setup fails with a clear error.