TSServer immediately exiting with SIGTERM

Bug Reports
1

Just started having Cursor kill my TSServer, it shows all my types and hits (Loading...) and then it all goes away. I initially thought it was all hover/hits, but my JSON schema stuff works just fine, and narrowed it to the TSServer (I presume something maybe about TSServer itself is breaking because even when it’s being managed by the Vue extension, the Vue extension loses all typescript functionality similarly)

After re-installing it, it seemed to work for a short while before returning to this state, which is the oddest part.

:white_check_mark: This might be related to Intellisense infinite loading when using Cursor (Typescript)

:counterclockwise_arrows_button: I’m a little stumped on trying to figure out how it starts happening, I’d have to re-install again to try and get a definite trace, and I just got everything set up again, so I’d like to avoid that.

📷 TS Extension Log (Set to Debug; setting it to Trace just logs a bunch of no-response JSON for all the typescript extension's events, I also check the other output logs and didn't find anything that coincided)

2025-05-04 04:06:13.861 [info] Killing TS Server
2025-05-04 04:06:13.861 [info] Starting TS Server
2025-05-04 04:06:13.861 [info] Using tsserver from: c:\Users\me\AppData\Local\Programs\cursor\resources\app\extensions\node_modules\typescript\lib\tsserver.js
2025-05-04 04:06:13.861 [info] Forking…
2025-05-04 04:06:13.861 [info] Starting…
2025-05-04 04:06:13.861 [info] Forking…
2025-05-04 04:06:13.861 [info] Starting…
2025-05-04 04:06:13.862 [error] TSServer exited. Code: null. Signal: SIGTERM

I also tried setting it to use my globally installed version of typescript/lib and it had the same result

💻 System Info

Version: 0.49.6 (user setup)
VSCode Version: 1.96.2
Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50
Date: 2025-04-25T04:49:20.797Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

:prohibited: Yep, this is big enough I have to reopen VS Code

2

This probably doesn’t apply to all these instances of the issue, but for me I found that the Vue extension was killing the built-in typescript (like it should to take over for it as the TS language server), but then all my typescript files weren’t being provided language features by the extension so I was left with infinite loading and then nothing since there was to active TS language services covering the file.
It still loads fine in VS Code with the same settings and extensions, so there’s still something going on with cursor, but now I can use Cursor again as long as I turn off the Vue extension :person_facepalming: