New vue file will get Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser. when typescript 3.9-4.0 in VSCode
#2127
Comments
|
This will require some investigation - it should be work based on everything I understand. |
|
FWIW, I often get this error (usually on existing Vue single file components I've had open in the editor for a while) and then quitting and reopening VSCode makes it go away. It usually pops up again after a few hours, and I have no idea what's happening to trigger it though. |
You can downgrade TypeScript to 3.8 temporarily. |
|
The problem is still present with TypeScript 4.0.2 (2020-08-21) and 3.9.7 (2020-07-16). On the other hand, the older 3.8.3 (2020-02-28) works fine for me. @sheetalkamat You made a fix in TS related to 1813. Do you expect the change to fix this issue? If yes, in which TS release version will it be included? |
|
Vue is just not well supported by this project. I don't have any experience in Vue, and I don't have the cycles to learn Vue and investigate whilst also maintaining everything else. We'd love for someone from the Vue community to champion support. Without a champion, this will likely remain broken. |
|
I studied it. This is reason #2127 (comment). I open a issue and add a test in TypeScript project. |
|
This problem will solved in TypeScript 4.1 I will close issue when typescript 4.1 stable released. |
Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser. when typescript 3.9 in VSCodeParsing error: "parserOptions.project" has been set for @typescript-eslint/parser. when typescript 3.9-4.0 in VSCode
|
I'm also interested in helping with questions about Vue, TypeScript, ESLint. |
Uh oh!
There was an error while loading. Please reload this page.
This problem will effect typescript 3.9~4.0 .
Fixed in typescript 4.1 #2127 (comment)
Repro
https://github.com/yoyo930021/typescript-eslint-vue-bug
Expected Result
All correct.
Actual Result
Additional Info
Versions
@typescript-eslint/typescript-estree3.0.2TypeScript3.9.3node13.14.0npm6.14.4The text was updated successfully, but these errors were encountered: