ESLint Option Migration

Use a custom migrator only when an existing Biome rule should preserve meaningful ESLint options. Severity-only migration belongs to the generated rule mapping.

Preconditions

Confirm before editing:

1. The Biome rule and its option type already exist.
2. Rule metadata identifies the ESLint source rule.
3. Generated severity migration already exists or will be regenerated.
4. Official ESLint or plugin documentation establishes the exact option shape and defaults.
5. The supported Biome semantics are clear, including unsupported source options.

Load lint-rule-development when the Biome rule or its own options still need implementation.

Pipeline

Custom migration has four parts: