eslint-plugin-configs

To create an ESLint plugin supporting both flat config and eslintrc, you need to export rule configurations compatible with ESLint v8 and v9. This involves defining a unified plugin shape with meta, rules, and configs to ensure cross-version compatibility.

The required meta structure for an ESLint v9 flat config plugin mandates defining meta.name, meta.version, and meta.namespace. All config keys must use the namespace prefix to ensure the plugin integrates correctly with the flat config environment.

Scaffolding an ESLint plugin with consumer examples involves generating rules, flat and legacy configs, and optional processors. The generated plugin provides clear usage examples demonstrating how to consume it across both ESLint v8 eslintrc and v9 flat config workflows.

Yes, the ESLint plugin generator supports adding optional processors to the plugin scaffold. It generates or updates the plugin to export these processors alongside rules and configs while maintaining compatibility with both ESLint v8 and v9 environments.

ESLint plugin config keys require a namespace prefix in flat config to enforce a single plugin shape and prevent naming collisions. The meta.namespace property ensures all exported rule configurations are correctly scoped and recognized by the ESLint v9 engine.

Yes, you can update an existing ESLint plugin to support v9 flat config without breaking v8 compatibility. The generator updates the plugin to export both legacy and flat configs, reducing cross-version maintenance effort while providing migration guidance.