Update parserOptions.project for TypeScript files to be true
#98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change causes the
typescript-eslint
plugin to use thetsconfig.json
file nearest to file being linted, rather than thetsconfig.json
file located in the directory from which ESLint is launched.Without this change ESLint can break when multiple
tsconfig.json
files are present (e.g. in a monorepo) and a single file is being linted in isolation, especially in IDEs such as IntelliJ which will always launch ESLint from the project root directory.More info can be found at: