voidzero-dev / voidzero-dev/vite-plus
Also migrate dynamic Oxlint & Oxfmt configurations if they exist
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 261
- Avg merge
- 1d 34m
- Merged PRs (30d)
- 135
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
- [x] Read the [Contributing Guidelines](https://github.com/voidzero-dev/vite-plus/blob/main/CONTRIBUTING.md).
- [x] Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- [x] Check that there isn't already an issue requesting the same feature.
Contributor guide
Research direction
Locate the existing migration flows for Vitest and tsdown, then compare them with migration handling for .ox*rc.json(c) configurations. Add equivalent handling for oxlint.config.ts and oxfmt.config.ts when those files exist, and verify that both dynamic configurations migrate correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100