Build plugin/config relocation

ESLint config lookup starts from linted file directory monorepo packages resolve different config

Monorepo packages unexpectedly resolve a different or no config.

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: Config lookup now starts from linted file directory
Likely root cause: Monorepo packages unexpectedly resolve a different or no config.
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

Monorepo packages unexpectedly resolve a different or no config.

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 config lookup starts from linted file directory monorepo packages resolve different config
site:eslint.org "configuration file" "current working directory" "eslint.config.js"
ESLint configuration files eslint.config.js lookup
"v10_config_lookup_from_file"
https://eslint.org/docs/latest/use/configure/configuration-files
'Configuration File Resolution' in https://eslint.org/docs/latest/use/configure/configuration-files
https://eslint.org/blog/2024/08/eslint-v9.9.0-released/
https://eslint.org/docs/latest/use/migrate-to-10.0.0