Repository navigation
vp up in monorepo changes vite dependency in package.json from catalog to exact version #2309
Description
Describe the bug
In just-created vp monorepo with pnpm, package.json has dev dependency "vite": "catalog:".
By launching vp up, dependencies are updated properly in pnpm-workspace.yaml and vite is set there as:
catalog:
...
vite: npm:@voidzero-dev/vite-plus-core@0.2.7
...
but package.json vite dependency is changed from catalog: to npm:@voidzero-dev/vite-plus-core@0.2.7
What is expected:
After vp up package.json vite dependency should be preserved as "vite": "catalog:".
What happening actually:
After vp up package.json vite dependency is changed from "vite": "catalog:" to "vite": "npm:@voidzero-dev/vite-plus-core@0.2.7".
Reproduction
not required
Steps to reproduce
vp create vite:monorepo- selectpnpmas package manager and complete installing.- Check
package.json:vitedependency is set as"vite": "catalog:"there. - Run
vp up. - Check
package.json:vitedependency is changed now to"vite": "npm:@voidzero-dev/vite-plus-core@0.2.7", but should be preserved as"vite": "catalog:".
System Info
VP current env:
VITE+ - The Unified Toolchain for the Web
Environment:
Version 24.18.1
Source engines.node
Source Path /home/shanti/workspace/code/vite-plus-monorepo-deps-issue/package.json
Project Root /home/shanti/workspace/code/vite-plus-monorepo-deps-issue
Tool Paths:
node /home/shanti/.vite-plus/js_runtime/node/24.18.1/bin/node
npm /home/shanti/.vite-plus/js_runtime/node/24.18.1/bin/npm
npx /home/shanti/.vite-plus/js_runtime/node/24.18.1/bin/npx
Package Manager:
Name pnpm
Version 11.18.0
Source devEngines.packageManager
Source Path /home/shanti/workspace/code/vite-plus-monorepo-deps-issue/package.json
Project Root /home/shanti/workspace/code/vite-plus-monorepo-deps-issue
Bin Path /home/shanti/.vite-plus/package_manager/pnpm/11.18.0/pnpm/bin/pnpm
---
VP version:
VITE+ - The Unified Toolchain for the Web
vp v0.2.7
Local vite-plus:
vite-plus v0.2.7
Tools:
vite v8.1.5
rolldown v1.2.0
vitest v4.1.10
oxfmt v0.60.0
oxlint v1.75.0
oxlint-tsgolint v7.0.2001
tsdown v0.22.14
Environment:
Package manager pnpm v11.18.0
Node.js v24.18.1 (engines.node)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.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
None yet
Effort
None yet
Target date
None yet
Start date
None yet
Activity
test(snapshots): pin the #2309 repair fixture to an exact catalog ver…
test(snapshots): re-record the remaining pnpm override-key fixtures
test(snapshots): cover the #2309 fix on pnpm 12
fix(migrate): keep `catalog:` specs intact through `vp up` under pnpm
test(snapshots): pin the #2309 repair fixture to an exact catalog ver…
test(snapshots): re-record the remaining pnpm override-key fixtures
test(snapshots): cover the #2309 fix on pnpm 12
docs: simplify the #2309 override-key prose
fix(migrate): address review findings on the #2309 override re-keying
fix(pm): keep Yarn `catalog:` references intact through `vp up`
fix(pm): keep Yarn `catalog:` references intact through `vp up`
fix(pm): keep Yarn `catalog:` references intact through `vp up`
fix(pm): keep Yarn `catalog:` references intact through `vp up`
fix(pm): keep Yarn `catalog:` references intact through `vp up`
fix(migrate): keep `catalog:` specs intact through `vp up` under pnpm
test(snapshots): pin the #2309 repair fixture to an exact catalog ver…
test(snapshots): re-record the remaining pnpm override-key fixtures
test(snapshots): cover the #2309 fix on pnpm 12
docs: simplify the #2309 override-key prose
fix(migrate): address review findings on the #2309 override re-keying
refactor(migrate): simplify the #2309 override re-keying helpers
fix(migrate): keep `catalog:` specs intact through `vp up` under pnpm (…