You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
peerDependencies oxc-transform-react range (^0.145.0) is out of date, breaks npm install after [email protected] #1437
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/[email protected] 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).
I think it depends on how Oxc will maintain the compat. Maybe like >=0.145.0,<0.150.0 so that Oxc can still introduce breaking changes in once a 5 version 🤔
Activity
ArnaudBarre commentedon Aug 25, 2026
@sapphi-red I think we should have it as a dependency and then later rolldown can drop fast refresh from core?
sapphi-red commentedon Aug 27, 2026
I'm a bit hesitant to do so given that the react compiler feature and the package is still experimental.
sapphi-red commentedon Aug 27, 2026
refs oxc-project/oxc#26033
ArnaudBarre commentedon Aug 27, 2026
Should we use
=>0.145.0in the range in the meantime?sapphi-red commentedon Aug 27, 2026
I think it depends on how Oxc will maintain the compat. Maybe like
>=0.145.0,<0.150.0so that Oxc can still introduce breaking changes in once a 5 version 🤔ArnaudBarre commentedon Aug 27, 2026
@Boshen any opinion on this?
piotr-cz commentedon Aug 31, 2026
For the time being, such override in package.json should fix it:
{ "overrides": { "@babel/plugin-transform-runtime": "^7.29.7" } }nstepien commentedon Sep 4, 2026
TBH it is an experimental package so I think it's fine to allow a broader range and expect breaking changes 🤷♂️
rakleed commentedon Oct 6, 2026
@Boshen @ArnaudBarre @sapphi-red any thoughts on how to resolve this better?