TypeScript Server Error (5.2.2) on update to 1.82.0

[TonyGravagno]

Not sure if this can be reproduced yet. Just updated VSCode which includes TypeScript 5.2.2 and this error occurred. Will modify/update this report with proper process and logs if I can get more info. Given the extensions reported in this error, it's not apparent to me yet if this is a VSCode issue or an extensions issue, but "something" in the new update just broke "something", and I'm starting here with the diagnostics. Will also advise extension authors.

<semantic> TypeScript Server Error (5.2.2)
Debug Failure. False expression.
Error: Debug Failure. False expression.
    at _NodeTypingsInstaller.installPackage (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:186191:13)
    at TypingsCache.installPackage (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:175906:27)
    at ConfiguredProject2.installPackage (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:176180:30)
    at applySingleCodeActionCommand (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:144424:39)
    at Proxy.applyCodeActionCommand (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:144419:96)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\mxsdev.typescript-explorer-0.4.2\node_modules\@ts-type-explorer\typescript-plugin\dist\index.js:15:15)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-extract-object-binding-type-literal-plugin\index.js:21:26)
    at proxy.<computed> [as applyCodeActionCommand] (c:\Users\tonyg\.vscode\extensions\paulshen.paul-typescript-toolkit-0.0.6\node_modules\typescript-react-utils-plugin\index.js:21:26)
    at IpcIOSession.applyCodeActionCommand (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:184567:36)
    at applyCodeActionCommand (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:182680:43)
    at c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:184838:69
    at IpcIOSession.executeWithRequestId (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:184830:14)
    at IpcIOSession.executeCommand (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:184838:29)
    at IpcIOSession.onMessage (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:184880:51)
    at process.<anonymous> (c:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js:186461:14)
    at process.emit (node:events:513:28)
    at emit (node:internal/child_process:937:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

Version: 1.82.0 (system setup)
Commit: 8b617bd08fd9e3fc94d14adb8d358b56e3f72314
Date: 2023-09-06T22:07:07.438Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045

Current scenario: I just opened an existing workspace with a TypeScript / React project. Linting was reporting that lodash is not installed, but it is, and I believe this error displayed during a rebuild.

I will reload the environment to see if this reproduces, and will test with and without the extensions shown in the error to see if either one of them triggers the issue.

[andrewbranch]

The extensions in the stack trace are definitely a red flag to me; we often see proxying extensions like these fail to pass through all parameters and break after an internal API change in TS. I think that’s more than likely what’s happening, but let me know if you can reproduce with those extensions disabled.

[ilyvion]

I don't know if it's the same exact cause, but I'm also having trouble with VSCode after upgrading to TypeScript 5.2.2 (from 4.9.5) (I'm using "workspace version" rather than VSCode version, but my workspace version now happens to also be 5.2.2) with error messages that are exactly the same, even though the stack trace isn't. In 4.9.5, I didn't have any issues, but now, I intermittently and seemingly randomly start getting errors like this in the "Extension Host" log:

2023-09-13 08:58:09.467 [error] [vscode.typescript-language-features] provider FAILED
2023-09-13 08:58:09.467 [error] Error: <semantic> TypeScript Server Error (5.2.2)
Debug Failure. False expression.
Error: Debug Failure. False expression.
    at ConfiguredProject2.updateGraphWorker (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:176958:11)
    at ConfiguredProject2.updateGraph (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:176817:32)
    at ConfiguredProject2.updateGraph (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:178072:24)
    at updateProjectIfDirty (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:178525:35)
    at ConfiguredProject2.getLanguageService (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:176428:7)
    at IpcIOSession.provideInlayHints (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:183663:27)
    at provideInlayHints (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:182825:43)
    at c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:184838:69
    at IpcIOSession.executeWithRequestId (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:184830:14)
    at IpcIOSession.executeCommand (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:184838:29)
    at IpcIOSession.onMessage (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:184880:51)
    at process.<anonymous> (c:\Users\alexs\Documents\Projects\qcext-client\node_modules\typescript\lib\tsserver.js:186461:14)
    at process.emit (node:events:513:28)
    at emit (node:internal/child_process:937:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
	at n.create (c:\Users\alexs\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\typescript-language-features\dist\extension.js:2:860352)
	at g.w (c:\Users\alexs\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\typescript-language-features\dist\extension.js:2:855676)
	at g.u (c:\Users\alexs\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\typescript-language-features\dist\extension.js:2:854759)
	at ChildProcess.<anonymous> (c:\Users\alexs\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\typescript-language-features\dist\extension.js:2:854391)
	at ChildProcess.emit (node:events:513:28)
	at emit (node:internal/child_process:937:14)
	at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

and once this happens, I have to run the VSCode command TypeScript: Reload Project to get things back to normal. Sometimes I can code for an hour without it happening, and other times it happens after just a few minutes, but it keeps happening at irregular intervals. I notice it having happened mainly by Intellisense suddenly showing garbage. For instance, if I hover over action here, it tells me:

but moving over to payload, it loses the plot:

and here it is again after running TypeScript: Reload Project:

EDIT: Oh, just for completeness, here's my VSCode data, too:
Version: 1.82.0 (user setup)
Commit: 8b617bd08fd9e3fc94d14adb8d358b56e3f72314
Date: 2023-09-06T22:07:07.438Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045

EDIT 2: I also just noticed version 1.82.1 was released, so I'll update to that one and see if the problem still remains.

[andrewbranch]

@alexschrod that is definitely a totally different code path, but if you can repro it reliably, we’ll take a repro (preferred) or TS Server logs!

[Daydreamer-riri]

@alexschrod I encountered the same mistake.

@andrewbranch I've been able to consistently reproduce this problem in all of my repo using typescript@5.2.2(workspace versioin)

[andrewbranch]

Can you provide a repo and instructions on how to reproduce?

[juancampa]

I've also run into this issue with typescript 5.2.2 (The second callstack in this issue posted by @alexschrod). I spent some time debugging the ts server locally, and this is what I've gathered so far, in case it's useful:

• This is the assertion being triggered
• I also have a plugin. My plugin calls languageService.getProgram() which triggers the creation of a new Program, which in turn causes the above assertion to fail in updateGraphWorker (because the old program and the new program are different objects)
• Work around: The assertion doesn't happen if I use languageService.getCurrentProgram() instead. However, this seems like a private API function, so it's not listed in tsserverlibrary. This is definitely hacky and I'm not sure if its masking other issues.

[Daydreamer-riri]

Can you provide a repo and instructions on how to reproduce?

I found my problem due to TypeScript-Plugin-CSS-MODULES. I no longer use it anymore

[sheetalkamat]

The plugins shouldnt be using languageService.getProgram() instead project.getProgram() to ensure there is no issue with synchronization between LS and project. This looks like external issue with the plugin rather than Typescript itself