Add tsconfig parserOptions only for ts,tsx
chore(eslint): add tsconfig parserOptions only for ts,tsx
Add tsconfig parserOptions only for ts,tsxchoreadd tsconfig parseroptions only tsx eslint
Committed by with-heart
commit message
chore(eslint): add tsconfig parserOptions only for ts,tsx
`eslint` complains about `parserOptions.project` configuration in files
that aren't specified in `tsconfig.json` (like `babel.config.js`). This
change moves the parser configuration to an `overrides` section
specifically for `ts` and `tsx` files.Editor assessment
The subject states the change precisely: tsconfig parserOptions are applied only to ts and tsx files in the ESLint config. The body then explains the actual problem and the design: eslint complained about parserOptions.project for files not covered by tsconfig.json such as babel.config.js, so the parser configuration moved into an overrides section scoped to ts and tsx. Symptom, cause, and remedy in four lines, with the eslint scope correctly naming the tooling. No footers needed. An exemplary config-fix commit. No separate scope field is needed since the eslint scope already anchors the tooling context precisely.