You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Deno extension kills the TSserver To Reproduce
Install Deno extension in vscode
Make sure Deno extension is enabled
Create a typescript file with a function in it and see if it gives you intellisense for that function
It should not give any intellisense because Deno extension is crashing TSserver
Expected behavior
Extension should not crash TSserver.
Screenshots
Deno extension is installed but not enabled and TSserver has not yet crashed according to the output log:
Demonstrating that intellisense is working in a typescript file extensions is not enabled:
Deno extension gets enabled and output log shows that TSserver has crashed:
Demonstrating the intellisense no longer works in a typescript file:
Versions
vscode: 1.95.1 (I also tried 1.95.3, same outcome)
commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
deno extension: v3.42.0
deno version: 2.0.1
macOS sonoma 14.5
The text was updated successfully, but these errors were encountered:
As a workaround for anyone else stumbling upon this, you can enable the extension only for certain workspace so it does not break other projects with the "Enable (workspace)" option.
Describe the bug
Deno extension kills the TSserver
To Reproduce
Expected behavior
Extension should not crash TSserver.
Screenshots
Deno extension is installed but not enabled and TSserver has not yet crashed according to the output log:
Demonstrating that intellisense is working in a typescript file extensions is not enabled:
Deno extension gets enabled and output log shows that TSserver has crashed:
Demonstrating the intellisense no longer works in a typescript file:
Versions
vscode: 1.95.1 (I also tried 1.95.3, same outcome)
commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
deno extension: v3.42.0
deno version: 2.0.1
macOS sonoma 14.5
The text was updated successfully, but these errors were encountered: