vp update warns about issues with vite peer dependency

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.

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"
      ]
    }
  }

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

@wesbos

@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.

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"
      ]
    }
  }

Please refer to this workaround.

Navigation Menu

Repository navigation

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

Describe the bug

Reproduction

Steps to reproduce

System Info

Used Package Manager

Logs

Validations

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

vp update warns about issues with vite peer dependency #1021

Description

Describe the bug

Reproduction

Steps to reproduce

System Info

Used Package Manager

Logs

Validations

Activity

fengmk2 commented on Mar 18, 2026

wesbos commented on Mar 18, 2026

fengmk2 commented on Mar 23, 2026

rozsazoltan commented on Mar 23, 2026

Boshen commented on May 18, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

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