
@dd-pardal
is a previously reported issue #60 , you can disable the extension in works space when you don't work with deno
Yes, when the extension is disabled this does not happen, but the extension shouldn't lint JavaScript files like that, I think. Also, for some reason, now it doesn't lint anything at all. It just keeps "Initializing JS/TS language features".
which version of vscode do you have?
@buttercubz 1.45.1
in vscode command line type typescript: restart ts server when this happen
@buttercubz
I think being required to disable deno extension for every non-deno typescript project is too much. Is there a way to disable this plugin by default and enable only for my deno workspaces?
Today I was working on a nodejs workspace and VSCode gave me a weird import error in my ts file. I was surprised to find out that deno extension was parsing my ts code in a nodejs project.
@0916dhkim try adding "deno.enable": false to settings.json
@David-Else Thank you. I did not know about the setting.
It still does not fix the problem of linting JS as if they were TS
Default of deno.enable is false now. This should be resolved.
Most helpful comment
It still does not fix the problem of linting JS as if they were TS