eslint-migrate-options

Use a migration framework that deserializes ESLint rule options into Biome-compatible configurations. This process translates non-severity settings through type-safe mappings and plugin-specific option structs rather than simply mapping severities.

Non-severity ESLint options are configurable rule settings beyond error levels. They require deserialization and translation into Biome rule options using custom option mappings and plugin-specific structs to preserve their original behavior accurately.

Yes, migrating ESLint options to Biome requires the migration framework located in crates/biome_cli. This framework provides the necessary structure to deserialize options and ensure type-safe mappings for plugin-specific configurations.

To ensure type-safe mappings when translating ESLint plugin options to Biome, define plugin-specific option structs and follow recommended workflows with thorough testing. This validates that deserialized configurations correctly map to Biome rules.

The best way to test ESLint to Biome rule option migrations is to follow the recommended testing practices defined in the migration workflow. This involves validating deserialized plugin-specific options against expected Biome configurations to ensure accurate translations.