TanStack Intent Yarn PnP Reproduction

Minimal reproduction for TanStack Intent discussion #119.

Environment

• Yarn PnP is enabled with nodeLinker: pnp in .yarnrc.yml.
• There is intentionally no node_modules directory.
• The project depends on @tanstack/react-start@1.167.52, which is listed in the Intent registry with 3 skills.

Reproduce

corepack enable
yarn install
yarn prove:pnp
yarn repro

yarn prove:pnp confirms that Yarn PnP resolves the installed package and that the skill files exist inside the package archive.

Equivalent direct repro command:

bunx --bun @tanstack/intent@latest list

The Yarn dlx path can also be checked:

yarn dlx @tanstack/intent@latest list

Expected

Intent discovers @tanstack/react-start from the Yarn PnP dependency map and lists its 3 registered skills.

The Intent docs say list scans installed dependencies, including "Yarn PnP projects without node_modules".

Actual

With this PnP project, @tanstack/intent list reports no packages found even though @tanstack/react-start@1.167.52 is installed and published with skills.

Observed with bunx --bun @tanstack/intent@latest list:

No intent-enabled packages found.

The installed package does contain the expected skills:

found skills/lifecycle/migrate-from-nextjs/SKILL.md
found skills/react-start/SKILL.md
found skills/react-start/server-components/SKILL.md

or, if a stale empty node_modules directory exists:

No intent-enabled packages found.
Scanned: project node_modules

Notes

Creating an empty node_modules directory changes the reported scan source, but still does not discover packages:

mkdir node_modules
yarn repro
rm -rf node_modules