Build plugin/config relocation

ESLint flat config command line flags no longer available --ext --rulesdir --resolve-plugins-relative-to

CI fails on an option that remained accepted in older majors.

ESLintJavaScript toolingBuild plugin/config relocationeslint10

Agent Quick Fix

Repair against the current ESLint contract, then keep the change narrow and source-backed.

Product: ESLint
Current-contract area: Legacy CLI option removed under flat config
Likely root cause: CI fails on an option that remained accepted in older majors.
Repair direction: Verifier checks the current package identity/config format and a real transformed output. Check the exact intended lint findings, not merely process exit 0.

Symptom

CI fails on an option that remained accepted in older majors.

Why This Happens

The old package/config name is syntactically valid, but current tool packaging and discovery rules live in external release documentation.

Common Wrong Fixes

Changing local code without checking the current external contract.
Retrying the same install, build, or API call with no version/source change.
Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

ESLint flat config command line flags no longer available --ext --rulesdir --resolve-plugins-relative-to
site:eslint.org docs latest use command line interface flat config --ext no longer available
https://eslint.org/docs/latest/use/configure/migration-guide
https://eslint.org/docs/v9.x/use/configure/migration-guide#cli-flag-changes
eslint v9 migration guide CLI Flag Changes --ext
ESLint "Invalid option '--ext'" flat config no longer supported
https://eslint.org/docs/v8.x/use/configure/configuration-files-new#cli-flag-changes
site:eslint.org/docs/v8.x/use/configure/configuration-files-new CLI Flag Changes --ext flat config