voidzero-dev / voidzero-dev/vite-plus

Support ESLint migration for monorepo workspace packages

Aperta
#1,168 0 commenti 4 reazioni 1 assegnatario Rivendicata da @fengmk2 Vedi su GitHub
migration
Lingua principale
Rust
Stelle
5.8k
Fork
261
Merge medio
1g 34m
PR unite (30g)
135

Descrizione

## Feature Request

### Problem

When migrating a monorepo to Vite+, the ESLint migration only looks for a root config:

> ESLint detected in workspace packages but no root config found. Package-level ESLint must be migrated manually.

In monorepos like [TresJS](https://github.com/Tresjs/tres), ESLint is configured per-package using a shared config (`@tresjs/eslint-config` wrapping `@antfu/eslint-config`) with custom rules (Vue attribute limits, curly braces, stylistic formatting, etc.). There's no root-level ESLint config — each package has its own `eslint.config.mjs`.

The current migration doesn't iterate over workspace packages to migrate them individually.

### Real-world example

- Monorepo: https://github.com/Tresjs/tres
- Shared config: `@tresjs/eslint-config` (wraps `@antfu/eslint-config`)
- Custom rules include: Vue attribute limits, curly braces enforcement, stylistic formatting
- Each package (`core`, `cientos`, `nuxt`, `post-processing`, etc.) has its own `eslint.config.mjs` importing the shared config

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.