Skip to content

fix: scope ESLint parserOptions.project to real tsconfigs only#1643

Merged
damyanpetev merged 1 commit intodpetev/update-wcfrom
copilot/fix-tsconfig-parsing-errors
Apr 20, 2026
Merged

fix: scope ESLint parserOptions.project to real tsconfigs only#1643
damyanpetev merged 1 commit intodpetev/update-wcfrom
copilot/fix-tsconfig-parsing-errors

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 20, 2026

parserOptions.project: '**/tsconfig.json' is resolved by the TypeScript parser independently of ESLint's ignores — template tsconfigs under **/files/** were still loaded even though those .ts files were excluded from linting. One of those template tsconfigs uses erasableSyntaxOnly (TS 5.5+), which the linter's TypeScript version doesn't recognise, causing a parse error on every linted file.

Changes

  • eslint.config.mjs: Replace the wildcard project glob with an explicit list of the three real tsconfigs the linter should operate on.
// before
project: '**/tsconfig.json',

// after
project: ['tsconfig.json', 'packages/ng-schematics/tsconfig.json', 'packages/igniteui-mcp/igniteui-doc-mcp/tsconfig.json'],

Note: !-prefixed negation patterns in parserOptions.project are silently ignored by @typescript-eslint/parser v8, so an explicit allowlist is the only reliable approach here.

@damyanpetev damyanpetev marked this pull request as ready for review April 20, 2026 17:40
@damyanpetev damyanpetev merged commit 3554ac4 into dpetev/update-wc Apr 20, 2026
1 check passed
@damyanpetev damyanpetev deleted the copilot/fix-tsconfig-parsing-errors branch April 20, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants