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, 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
Feature Request
Problem
When migrating a monorepo to Vite+, the ESLint migration only looks for a root config:
In monorepos like TresJS, ESLint is configured per-package using a shared config (
@tresjs/eslint-configwrapping@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 owneslint.config.mjs.The current migration doesn't iterate over workspace packages to migrate them individually.
Real-world example
@tresjs/eslint-config(wraps@antfu/eslint-config)core,cientos,nuxt,post-processing, etc.) has its owneslint.config.mjsimporting the shared config