getASTFromProject reports error when linting new files using a long running instance of eslint #959
Labels
bug
Something isn't working
duplicate
This issue or pull request already exists
package: parser
Issues related to @typescript-eslint/parser
What code were you trying to parse?
The file is empty and just created in vs code - the eslint extension is working on a newly created file.
What did you expect to happen?
There should be no errors (like if setting the parser option
"createDefaultProgram": true
)What actually happened?
The VSCode extension returns:
(Running eslint from the terminal works as expected - it might be a caching issue)
Versions
@typescript-eslint/parser
2.1.0
TypeScript
3.5.3
ESLint
6.3.0
node
10.16.3
npm
6.9.0
yarn
1.7.3
.eslintrc.json
```json { "parser": "@typescript-eslint/parser", "plugins": [ "react", "@typescript-eslint" ], "extends": [ "eslint:recommended", "plugin:@typescript-eslint/eslint-recommended", "plugin:@typescript-eslint/recommended", "plugin:@typescript-eslint/recommended-requiring-type-checking" ], "parserOptions": { "project": "tsconfig.json", "ecmaFeatures": { "jsx": true }, "ecmaVersion": 2018, "sourceType": "module" }, "env": { "browser": true, "es6": true }, "globals": { "Atomics": "readonly", "SharedArrayBuffer": "readonly" }, "rules": { "indent": [ "error", "tab" ], "linebreak-style": [ "error", "unix" ], "quotes": [ "error", "double" ], "semi": [ "error", "always" ] } } ```
tsconfig.json
```json { "compilerOptions": { "target": "es5", "module": "esnext", "jsx": "preserve", "outDir": "./dist", "strict": true, "esModuleInterop": true, "allowJs": true, "lib": [ "dom", "dom.iterable", "esnext" ], "skipLibCheck": true, "allowSyntheticDefaultImports": true, "forceConsistentCasingInFileNames": true, "moduleResolution": "node", "resolveJsonModule": true, "isolatedModules": true, "noEmit": true }, "include": [ "src" ] } ```
References:
Possible related to:
If needed I can investigate further and make a pull request solving the issue - but I would like to get a direction on where to best solve the issue.
The text was updated successfully, but these errors were encountered: