Yarn 4.x nodeLinker: node-modules – Will PnP remain the sole default?

No, Yarn 4.x maintains Plug’n’Play (PnP) as the default resolution strategy.

While the introduced nodeLinker: node-modules option provides an escape hatch for legacy environments, it does not signal a shift away from PnP as the core recommendation.

The Current Strategy

Yarn's architectural direction remains centered on PnP to solve the inherent issues of the node_modules structure, such as phantom dependencies and slow installation times. The node-modules linker is a compatibility layer designed specifically for tooling—like certain native addon build scripts or older bundlers—that cannot yet interpret the PnP dependency map.

Why PnP remains the Default

There is currently no official signal in the Yarn roadmap to drop support for the node-modules linker. In fact, the existence of the option suggests that Yarn acknowledges the reality of a fragmented ecosystem. As long as the Node.js experimental loader API continues to evolve, Yarn will likely offer PnP as the primary path for modern workflows while maintaining node-modules as a fallback for legacy compatibility.

How to verify and configure your linker

If your project requires a physical directory structure to function, you must explicitly set the linker. Follow these steps:

<

• Open your .yarnrc.yml file in your project root.
n
• Add or modify the following line:

  nodeLinker: node-modules

• Run yarn install to regenerate the dependency structure.

To verify which linker is currently active, use the following command in your terminal:

yarn config get nodeLinker

Assumptions and Uncertainty

The stability of PnP is partially tied to the evolution of the Node.js loader API. While Yarn abstracts much of this complexity, significant changes in how Node.js handles ESM resolution could impact how PnP is implemented. If Node.js were to introduce a native, high-performance alternative to PnP in the future, Yarn might shift its default then, but no such threshold currently exists.