Repository navigation
Also migrate dynamic Oxlint & Oxfmt configurations if they exist #2430
Description
Description
From what I can see it seems like oxlint.config.ts and oxfmt.config.ts doesn't have a migration flow yet. This seems like a bit of low-hanging fruit.
Suggested solution
Probably replicate how Vitest & tsdown are migrated.
Alternative
Manual migration, but we already have their .ox*rc.json(c) versions migratable, why not these ones too?
Additional context
No response
Validations
- Read the Contributing Guidelines.
- Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- Check that there isn't already an issue requesting the same feature.
Reacted by Cristian Rosescu
Activity
simulacre7 commentedon Aug 21, 2026
I'd like to take this one.Withdrawn — I missed that #2483 already implements this. Leaving my empirical findings as review feedback over there.fengmk2 commentedon Oct 14, 2026
The v1.2.0 ecosystem smoke test shows what the missing JS-config migration costs today. Each case also reproduces with the v1.1.0 migrate.
oxfmt,oxlint, andoxlint-tsgolintare dropped frompackage.jsoneven thoughoxfmt.config.ts,oxlint.config.ts, or project scripts import them, because detection only recognizes.oxfmtrc/.oxlintrcJSON files. react-doctor resolvesoxlintat runtime and its rule-registry script importsoxfmt(PR); dotabod-backend's configs import them (PR).fmt: {}and ignoresoxfmt.config.ts, so its own formatting pass uses defaults (double quotes, semicolons) and a project with single quotes and no semicolons failsvp fmt --checkon every file migrate touched (115 to 134 files). dotabod-frontend (PR), dotabod-backend (PR).vp fmt --config oxfmt.config.tsscripts stop working:Failed to load configuration file. Expected a \fmt` field in the default export of oxfmt.config.ts. The workaround is pointingvite.config.tsat the config and runningvp fmtwithout--config`.