Build plugin/config relocation
ESLint TypeScript configuration files eslint.config.ts jiti docs
eslint.config.ts works locally with one loader but fails in CI under the current ESLint runtime.
Agent Quick Fix
Repair against the current ESLint contract, then keep the change narrow and source-backed.
Product: ESLint
Current-contract area: TypeScript config loading path changes
Likely root cause: eslint.config.ts works locally with one loader but fails in CI under the current ESLint runtime.
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
eslint.config.ts works locally with one loader but fails in CI under the current ESLint runtime.
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.
site:eslint.org eslint.config.ts TypeScript configuration file jiti runtime current ESLint
ESLint TypeScript configuration files eslint.config.ts jiti docs
ESLint configure configuration files TypeScript eslint.config.ts
https://eslint.org/docs/latest/use/configure/configuration-files