Please support Yarn PnP
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 696
- Avg merge
- 8m
- Merged PRs (30d)
- 7
Description
Thank you to the team for their work on #308.
In the age of workspaces and AI agents I think Yarn PnP is more important than ever, and while symlinks might enable workarounds (idk for sure) the disk space savings of Yarn PnP have been the only way I've been able to make substantial progress with worktrees - otherwise my disk quickly fills.
Metro's lack of support for PnP is the main thing keeping any of my projects on node-linker config at this point and it would be a huge workflow unlock if Metro supported PnP proper.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing Metro's module-resolution and workspace handling, then determine the required Yarn PnP integration points. Done means Metro supports Yarn PnP without requiring a node-linker workaround, with coverage for the supported resolution cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100