Repository navigation
npx --package=vite-plus vp create does not work anymore with 1.1.0 #2920
Description
Describe the bug
npx --package=vite-plus vp create does not work anymore, see logs below. The 1.0.0 version still works (can be tested using npx --package=vite-plus@1.0.0 vp create).
> node --version
v26.10.0
> npm --version
11.19.1
> npx --package=vite-plus vp create
Need to install the following packages:
vite-plus@1.1.0
Ok to proceed? (y) y
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: undefined@undefined
npm error Found: vite-plus@1.0.0
npm error node_modules/vite-plus
npm error peerOptional vite-plus@"*" from oxfmt@0.70.0
npm error node_modules/oxfmt
npm error oxfmt@"=0.70.0" from vite-plus@1.0.0
npm error peerOptional vite-plus@"*" from oxlint@1.85.0
npm error node_modules/oxlint
npm error oxlint@"=1.85.0" from vite-plus@1.0.0
npm error 1 more (the root project)
npm error
npm error Could not resolve dependency:
npm error vite-plus@"1.1.0" from the root project
npm error
npm error Conflicting peer dependency: vitest@5.0.3
npm error node_modules/vitest
npm error peer vitest@"5.0.3" from @vitest/browser-playwright@5.0.3
npm error node_modules/@vitest/browser-playwright
npm error peerOptional @vitest/browser-playwright@"5.0.3" from vite-plus@1.1.0
npm error node_modules/vite-plus
npm error vite-plus@"1.1.0" from the root project
npm error peerOptional @vitest/browser-playwright@"5.0.3" from vitest@5.0.3
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/vhiairrassary/.npm/_logs/2026-10-07T08_37_12_104Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/vhiairrassary/.npm/_logs/2026-10-07T08_37_12_104Z-debug-0.log
Reproduction
Steps to reproduce
No response
System Info
-Used Package Manager
npm
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
vhiairrassary commentedon Oct 7, 2026
Maybe we just need to wait the next release of oxc, as it will include oxc-project/oxc#27385?
liangmiQwQ commentedon Oct 7, 2026
@vhiairrassary Thanks for your reporting, this is indeed a bug, and this is not just simply a dependency upgrade issue, I will collaborate with Oxc team to solve this.
As a work around, could you try this with a fresh npm cache? This might solve the problem temporarily.
npx --cache "$(mktemp -d)" --package=vite-plus@1.1.0 vp createvhiairrassary commentedon Oct 8, 2026
@liangmiQwQ Thank you for the workaround, I confirm it works as expected ✅
By the way, scaffolding fails when using
npmas package manager for both 1.0.0 and 1.1.0, but it is OK with yarn and pnpm. Do you want me to create an dedicated issues? I can reproduce on node 24 and 26.liangmiQwQ commentedon Oct 8, 2026
Thanks a lot! Perhaps it is not needed, I've gained a general understanding of the root cause of the issue.
npx --package=vite-plus vp createfails with exit 127 when npm is the chosen package manager #2970 as a duplicate of this issuenpx --package=vite-plus vp createfails with exit 127 when npm is the chosen package manager #2970 as a duplicate of this issue