Describe the bug
Svelte for VS Code extension v105.9.0 seems to have introduced a bug with JS/TS scripts which results in linting completely breaking. Errors and warnings are not being updated realtime nor on file save. After a few code changes hover tooltips are showing content for different lines in the document. Snippets and completion are not working properly and are suggesting content for source code that was originally loaded in specific line in the file.
Reloading the editor helps only until the code is edited, after which another reload is requred.
To Reproduce
Install version v105.9.0 of the extension.
Edit the source code, introduce some errors and check tooltips.
Expected behavior
Screenshots
Window object reference right after a reload:
After changing the window reference to an invalid piece of code, there are no errors, warnings and hints still suggest this is a window object.
After a reload:
Errors/warning basically sit in place(?) Which looks like linting is done only on initial load and then stops.
System:
OS: Windows 10 21H2 (build 19044.14.15)
IDE: VSCode 1.63
Plugin/Package: "Svelte for VSCode",
Node: v16.10.0
Additional context
Linting is only being done once per file and then requires an editor reload - This would suggest why errors "stay in place" after editing the source code.
Describe the bug Svelte for VS Code extension v105.9.0 seems to have introduced a bug with JS/TS scripts which results in linting completely breaking. Errors and warnings are not being updated realtime nor on file save. After a few code changes hover tooltips are showing content for different lines in the document. Snippets and completion are not working properly and are suggesting content for source code that was originally loaded in specific line in the file. Reloading the editor helps only until the code is edited, after which another reload is requred.
To Reproduce
Expected behavior
Screenshots Window object reference right after a reload:
After changing the window reference to an invalid piece of code, there are no errors, warnings and hints still suggest this is a window object.
After a reload:
Errors/warning basically sit in place(?) Which looks like linting is done only on initial load and then stops.
System:
Additional context Linting is only being done once per file and then requires an editor reload - This would suggest why errors "stay in place" after editing the source code.