vitejs / vitejs/vite-plugin-react
peerDependencies oxc-transform-react range (^0.145.0) is out of date, breaks npm install after oxc-transform-react@0.147.0
@Boshen is already working on this.
Since Aug 28, 2026.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 269
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 19
Description
Related plugins
Describe the bug
The published @vitejs/plugin-react@6.1.0 declares:
"peerDependencies": {
"oxc-transform-react": "^0.145.0"
}
oxc-transform-react has since been published at 0.147.0 on npm (https://www.npmjs.com/package/oxc-transform-react). Installing a project that has oxc-transform-react@^0.147.0 in its own dependencies together with @vitejs/plugin-react@6.1.0 now fails with ERESOLVE, because npm's default resolver won't satisfy a peer range of ^0.145.0 with 0.147.0 installed.
This is the same class of issue as #1144 (stale @rolldown/plugin-babel peer range).
Reproduction
https://stackblitz.com/edit/vitejs-vite-rudrnkqt?file=package.json
Steps to reproduce
- Open the reproduction link
- Open the terminal and run:
npm install
System Info
System:
OS: macOS 26.6.2
CPU: (12) arm64 Apple M3 Pro
Memory: 637.84 MB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.19.0 - /opt/homebrew/opt/node@24/bin/node
npm: 11.17.0 - /opt/homebrew/opt/node@24/bin/npm
bun: 1.4.0 - /opt/homebrew/bin/bun
Browsers:
Chrome: 152.0.7977.65
Safari: 26.6.2
npmPackages:
@vitejs/plugin-react: ^6.1.0 => 6.1.0
oxc-transform-react: ^0.147.0 => 0.147.0
vite: ^8.2.2 => 8.2.2
Used Package Manager
npm
Logs
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a Vite issue and not a framework-specific issue.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.