migrate-oxlint

To migrate an ESLint config to Oxlint, use a migration tool that reads your existing eslint.config.js and outputs a ready .oxlintrc.json file. It maps plugins and rules while validating options like --type-aware and --with-nursery for a smooth linting transition.

Yes, switching to Oxlint guides mapping ESLint plugins to Oxlint equivalents and handles plugins without direct mappings. It translates your existing rule configurations into the .oxlintrc.json format, preserving your lint behavior during the transition.

Handling eslint.config.js migration for a monorepo involves generating a unified .oxlintrc.json file that accommodates your project structure. The migration process includes a dry-run style overview to validate rule mappings and options before applying changes.

Oxlint migration supports type-aware linting by validating the --type-aware option during config generation. This ensures your migrated .oxlintrc.json file accurately reflects type-dependent rules from your original ESLint setup.

You can preview Oxlint config changes by using the --details option, which provides a dry-run style overview of the migration. This shows how your ESLint rules and plugins are mapped before the final .oxlintrc.json is generated.

A key limitation when migrating ESLint plugins to Oxlint is handling plugins without direct Oxlint equivalents. The migration process provides guidance messages for these gaps, but some custom or unsupported rules may require manual configuration or replacement.