`vp update` warns about issues with `vite` peer dependency

[nofxboy1234]

Describe the bug

When I update dependencies, it shows:

 WARN  Issues with peer dependencies found
.
└─┬ vite-plus 0.1.12
└─┬ @voidzero-dev/vite-plus-test 0.1.12
└── ✕ unmet peer vite@"^6.0.0 || ^7.0.0 || ^8.0.0-0": found 0.1.12
Done in 1.2s using pnpm v10.32.1

I'd expect pnpm to know that vite-plus is aliasing vite

Reproduction

https://github.com/nofxboy1234/vp-temp1

Steps to reproduce

Run vp update

System Info

`vp env current`:

VITE+ - The Unified Toolchain for the Web

Environment:
  Version  24.14.0
  Source   lts

Tool Paths:
  node  /home/dylan/.vite-plus/js_runtime/node/24.14.0/bin/node
  npm   /home/dylan/.vite-plus/js_runtime/node/24.14.0/bin/npm
  npx   /home/dylan/.vite-plus/js_runtime/node/24.14.0/bin/npx

`vp --version`:

VITE+ - The Unified Toolchain for the Web

vp v0.1.12

Local vite-plus:
  vite-plus  v0.1.12

Tools:
  vite             v8.0.0
  rolldown         v1.0.0-rc.9
  vitest           v4.1.0
  oxfmt            v0.40.0
  oxlint           v1.55.0
  oxlint-tsgolint  v0.17.0
  tsdown           v0.21.3

Environment:
  Package manager  pnpm v10.32.1
  Node.js          Not found

Used Package Manager

pnpm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[fengmk2]

Should add peerDependencyRules to pnpm field at package.json, I will fix vp create template too.

"pnpm": {
    "overrides": {
      "vite": "npm:@voidzero-dev/vite-plus-core@latest",
      "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
    },
    "peerDependencyRules": {
      "allowAny": [
        "vite",
        "vitest"
      ]
    }
  }

[wesbos]

are the overrides supposed to stay in the package.json? I think I iniitally was on Vite 7 when I migrated, and now im on vite 8. Unsure if I should keep them.

BTW this error also popped up for me but the allowany rule fixed it

[fengmk2]

@wesbos Because overriding Vite through overrides causes the package manager to see the Vite+ version, it leads to unmet peer dependency rule warnings. Currently, this can only be overridden by using the allowAny rule.

[rozsazoltan]

Until a proper solution is available, pnpm can still be manipulated in an automated way. Just create .pnpmfile.cjs and override @voidzero-dev/vite-plus-core version dynamically with bundledVersions.vite.

This makes it possible to retrieve the actual Vite version from bundledVersions.vite, and then use it to add VitePlus support only to packages that truly support that specific version. So if bundledVersions.vite is v8, but you install a dependency that only supports Vite 5-7, you will still receive the warning.

.pnpmfile.cjs (in your project root)

let vitePlusCoreVersion = null;
let bundledVite = null;
const logs = [];

// pnpm alias resolves vite instead of @voidzero-dev/vite-plus-core, try both paths
const candidates = [
  "./node_modules/vite/package.json",
  "./node_modules/@voidzero-dev/vite-plus-core/package.json",
];

for (const candidate of candidates) {
  try {
    const viteCore = require(candidate);
    if (viteCore.name === "@voidzero-dev/vite-plus-core") {
      vitePlusCoreVersion = viteCore.version;
      bundledVite = viteCore.bundledVersions?.vite;
      logs.push(`Loaded from ${candidate}: ${vitePlusCoreVersion} (bundled vite: ${bundledVite})`);
      break;
    }
  } catch {}
}

if (!bundledVite) {
  logs.push("vite-plus-core not found, peer dependency ranges will not be extended");
}

function satisfiesRange(version, range) {
  const bundledMajor = parseInt(version.split(".")[0], 10);
  const majorsInRange = [...range.matchAll(/\^?(\d+)/g)].map(m => parseInt(m[1], 10));
  return majorsInRange.includes(bundledMajor);
}

function extendViteRange(pkg, field) {
  const deps = pkg[field];
  if (!deps?.vite || !bundledVite || !vitePlusCoreVersion) return;

  if (satisfiesRange(bundledVite, deps.vite)) {
    logs.push(`${pkg.name}[${field}]: ${deps.vite} || ${vitePlusCoreVersion}`);
    deps.vite = `${deps.vite} || ${vitePlusCoreVersion}`;
  }
  // If the range does not match, the package does not support the vite version specified
  // in bundledVersions - this is more precise than blindly allowing all vite-plus-core
  // versions via ^0 or adding them manually one by one.
}

function readPackage(pkg) {
  extendViteRange(pkg, "dependencies");
  extendViteRange(pkg, "devDependencies");
  extendViteRange(pkg, "peerDependencies");
  return pkg;
}

function afterAllResolved(lockfile) {
  if (logs.length) {
    console.log("\n[Fix Vite version]\n" + logs.join("\n") + "\n\n");
  }
  return lockfile;
}

module.exports = { hooks: { readPackage, afterAllResolved } };

Test 01

❯ vp install @tailwindcss/vite
VITE+ - The Unified Toolchain for the Web

Progress: resolved 128, reused 60, downloaded 0, added 0

[Fix Vite version]
Loaded from ./node_modules/vite/package.json: 0.1.13 (bundled vite: 8.0.1)
@tailwindcss/vite[devDependencies]: ^8.0.0 || 0.1.13
@tailwindcss/vite[peerDependencies]: ^5.2.0 || ^6 || ^7 || ^8 || 0.1.13
@voidzero-dev/vite-plus-test[peerDependencies]: ^6.0.0 || ^7.0.0 || ^8.0.0-0 || 0.1.13

Packages: +14
++++++++++++++
Progress: resolved 130, reused 62, downloaded 0, added 0, done

dependencies:
+ @tailwindcss/vite 4.2.2

Done in 1.2s using pnpm v10.32.1

tip: Available short aliases: i = install, rm = remove, un = uninstall, up = update, ls = list, ln = link

Test 02

❯ vp install @tailwindcss/vite@4.1
VITE+ - The Unified Toolchain for the Web

Progress: resolved 136, reused 57, downloaded 1, added 0

[Fix Vite version]
Loaded from ./node_modules/vite/package.json: 0.1.13 (bundled vite: 8.0.1)
@voidzero-dev/vite-plus-test[peerDependencies]: ^6.0.0 || ^7.0.0 || ^8.0.0-0 || 0.1.13

Packages: +7 -5
+++++++-----
Progress: resolved 142, reused 63, downloaded 1, added 7, done
 WARN  Issues with peer dependencies found
.
└─┬ @tailwindcss/vite 4.1.18
  └── ✕ unmet peer vite@"^5.2.0 || ^6 || ^7": found 0.1.13

dependencies:
- @tailwindcss/vite 4.2.2
+ @tailwindcss/vite 4.1.18 (4.2.2 is available)

Done in 1.4s using pnpm v10.32.1

tip: Available short aliases: i = install, rm = remove, un = uninstall, up = update, ls = list, ln = link

Source: https://stackoverflow.com/a/79912585/15167500