voidzero-dev / voidzero-dev/vite-plus

Also migrate dynamic Oxlint & Oxfmt configurations if they exist

Offen
#2,430 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
contribution welcome
Vorherrschende Sprache
Rust
Sterne
5.8k
Forks
261
Ø Merge
1 T. 34 Min.
Gemergte PRs (30 T.)
135

Beschreibung

### 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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
typescript
Bereich
tooling
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
68/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.