Typescript-go error

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am using the cursor IDE for my typescript monorepo with pnpm.
I have installed the typescript-go plugin as the regular compiler is too slow for this large codebase.

Unfortunately, I am running into this error since a couple of weeks:
Request textDocument/semanticTokens/full failed. Message: InternalError: panic handling request textDocument/semanticTokens/full: semantic tokens: token spans multiple lines: start=(1685,4) end=(1686,6) for token at offset 70042 Code: -32603

There is a related issue in typescript-go’s github: Panic Alert Notification when Cursor edits some file and opening that file causes panic. · Issue #3621 · microsoft/typescript-go · GitHub

But they say that it should be solved and I should check with the IDE’s support.
So here I am :slight_smile:

Steps to Reproduce

Use a large Monorepo and have typescript-go plugin installed

Expected Behavior

I dont want to be spammed by error messages

Operating System

MacOS

Version Information

Version: 3.0.16
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z (3 wks ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

For AI issues: add Request ID with privacy disabled

Additional Information

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

This error comes from the typescript-go extension itself, not from Cursor. The panic in textDocument/semanticTokens/full happens when a semantic token spans multiple lines, which is a bug in the typescript-go LSP server.

Good news: a fix was merged upstream on May 2. It changes the behavior from panicking to gracefully skipping multi-line tokens.

To resolve this, update the TypeScript Native Preview extension to the latest version. You can do this from the Extensions panel (Cmd+Shift+X) by searching for the extension and clicking Update if one is available, or by reinstalling it.

If the error persists after updating, it may be worth opening a fresh issue on the typescript-go repo with an LSP trace.