-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension causes the TS Server to stop working #75
Comments
Hey @ma7moud3bas, |
I don’t know if this is related, but I spent an hour debugging why I couldn’t save this morning, and eventually through a process of elimination managed to get files to save after disabling this extension. I have some (maybe over complex) types in my code and I think an error in my TS may have caused this to happen? |
Not sure if related, but we work in a huge monorepo with seperate tsconfigs per package, and this extension was causing the server to crash as well every 10 or so minutes. Didn't have any issues saving though. But Typescript and intellisense would just break and I'd have to restart the extension host to get everything working again |
Could someone provide some type or project it's reproduced in please? |
Describe the bug
When the exteention is enabled, whenever I open vscode, the Typescript server starts to spin up but it never finishing spinning up. this behaviour makes the code editor unusable. I can't see linting or intellesense, the files don't save, and nothing works.
After disabling the extension, everything returned to normal.
This only started to happen Yesterday, Augest 23rd. before that, the extension was working normally.
Expected behavior
Everything should work normally.
The text was updated successfully, but these errors were encountered: