Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(migrate): detect Yarn PnP config even when env overrides nodeLinker

Open
#2,001 0 comments 0 reactions 1 assignee View on GitHub

@fengmk2 is already working on this.

Since Jul 1, 2026.

Assessment

This issue has not been assessed yet.

Description

bug

vp migrate currently treats YARN_NODE_LINKER=node-modules as enough to skip Yarn PnP handling. However, if the repository itself has .yarnrc.yml with nodeLinker: pnp, migration can complete successfully while leaving unsupported PnP config in the project. Future installs without that environment override will return to PnP mode.

Expected behavior:

  • If .yarnrc.yml explicitly sets nodeLinker: pnp, migration should not silently pass just because YARN_NODE_LINKER=node-modules is set.
  • Preferably, migration should stop and ask the user to change the project config manually, or apply the existing node-modules conversion flow if that is the intended behavior.
  • YARN_NODE_LINKER=pnp should still hard-block migration as today.

Suggested test:

Create a Yarn Berry fixture with:

# .yarnrc.yml
nodeLinker: pnp

Run migrate with:

YARN_NODE_LINKER=node-modules vp migrate --no-interactive

Assert that migration does not report the project as successfully migrated while leaving nodeLinker: pnp unchanged.

Dominant language
Rust
Stars
5.8k
Forks
263
Avg merge
1d 4h
Merged PRs (30d)
148

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.