Skip to content

Please support Yarn PnP #1928

Open
Open

Description

@Nantris

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.

Activity

  1. robhogan commented on Sep 17, 2026

    @robhogan
    Collaborator

    Thanks for opening this so we can freshly gauge the interest in Yarn PnP.

    I'm curious if you've tried nodeLinker: pnpm? It creates hard links in your project so (on linux or macos) it should use no extra disk space for each copy of a package+version on your machine, and it should be compatible with Metro out of the box.

  2. robhogan commented on Sep 17, 2026

    @robhogan
    Collaborator

    One significant stumbling block with Yarn PnP would be not so much in Metro but React Native - packages with native code would always need to be "unplugged", since xcode/gradle won't be able to read sources inside Yarn PnP's .zip archives. That seems to me like it'd be a devx headache and difficult to teach, and the unplugging itself would take away some of the disk space benefit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions