Change:
if (item === reportIssueItem) { const minModernTsVersion = this.versionProvider.bundledVersion.apiVersion; <del> if (minModernTsVersion && this.apiVersion.lt(minModernTsVersion)) { </del> <ins> if ( minModernTsVersion && previousState.type === ServerState.Type.Errored && previousState.error instanceof TypeScriptServerError && previousState.error.version.apiVersion?.lt(minModernTsVersion) ) { </ins> vscode.window.showWarningMessage( vscode.l10n.t("Please update your TypeScript version"), { modal: true, detail: vscode.l10n.t( <del> "The workspace is using an old version of TypeScript ({0}).nnBefore reporting an issue, please update the workspace to use the latest stable TypeScript release to make sure the bug has not already been fixed.", (previousState.type === ServerState.Type.Errored && previousState.error instanceof TypeScriptServerError ? previousState.error.version.apiVersion?.displayName : undefined) + ''), </del> <ins> "The workspace is using an old version of TypeScript ({0}).nnBefore reporting an issue, please update the workspace to use TypeScript {1} or newer to make sure the bug has not already been fixed.", previousState.error.version.apiVersion.displayName, minModernTsVersion.displayName), </ins> }); } else { const args = previousState.type === ServerState.Type.Errored && previousState.error instanceof TypeScriptServerError

Discussion:
Issue Type: <bBug</bOriginal error: When I click the Report Issue button I am shown: However 4.4.3 is the latest version of TypeScript released on npm. VS Code version: Code 1.60.2 (, 2021-09-22T11:59:08.826Z) OS version: Darwin arm64 20.6.0 Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (16)</summaryExtensionVersion ------ jison-syntax-highlight0.1.1 vscode-deno3.9.1 gitlens11.6.0 prettier-vscode9.0.0 lex-flex-yacc-bison0.0.3 nearley1.0.3 rust-analyzer0.2.751 vscode-docker1.17.0 python2021.9. vscode-pylance2021.9.3 jupyter2021.8. jupyter-keymap1.0.0 remote-containers0.194.0 cpptools1.6.0 makefile-tools0.2.2 vscode-jest4.1.2 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I wasn't able reproduce this in my testing. Are you still encountering this issue? If so, can you please share more info about your setup
if you know a way to trigger the TypeScript language server to crash I'll give it a go. At the time I upgraded to TypeScript which solved my issue but my code has changed enough in the interim that it no longer crashes under 4.4.3.
I can still reproduce this. I have a pending bug report in the TypeScript language service so you can use the same steps to trigger a crash: ! <summaryVisual Studio Code Version Info</summary<detailsVersion: 1.61.0 (user setup)<br/Commit: <br/Date: 2021-10-07T18:13:09.652Z<br/Electron: 13.5.1<br/Chrome: 91.0.4472.164 14.16.0<br/V8: 9.1.269.39-electron.0<br/OS: Windows_NT x64 10.0. </detailsAt this time, the is 4.4.3.

I stumbled upon this today ! Version: 1.63.0 Commit: Date: 2021-12-07T05:15:48.091Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 18.7.0 I tough this was a configuration error on my side but after a git checkout of a previously working config I can't solve the issue. I'm just unable to use typescript features, the ts server crashes continually after vscode lauch. This is my jsconfig:
This started happening to me too today - this is the only error log message I see when I turn on verbose logging:
Same.

Version: 1.63.2 Commit: Date: 2021-12-15T09:39:46.686Z Electron: 13.5.2 Chromium: 91.0.4472.164 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.11.0-49-generic TypeError: Cannot read property 'flags' of undefined at getPropertyOfObjectType () at getPropertyOfType () at resolveESModuleSymbol () at getTargetOfNamespaceImport () at getTargetOfAliasDeclaration () at resolveAlias () at getSymbol () at resolveNameHelper () at resolveName () at resolveEntityName () at getTargetOfExportSpecifier () at getTargetOfAliasDeclaration () at resolveAlias () at resolveSymbol () at mergeSymbol () at at Map.forEach (<anonymous) at mergeSymbolTable () at mergeSymbol () at at Map.forEach (<anonymous) at mergeSymbolTable () at initializeTypeChecker () at Object.createTypeChecker () at Object.getTypeChecker () at synchronizeHostData () at Object.getProgram () at ConfiguredProject.Project.updateGraphWorker () at ConfiguredProject.Project.updateGraph () at ConfiguredProject.updateGraph () at ProjectService.createLoadAndUpdateConfiguredProject () at ProjectService.assignProjectToOpenedScriptInfo () at at Object.flatMap () at ProjectService.applyChangesInOpenFiles () at <computed() at at IOSession.Session.executeWithRequestId () at IOSession.Session.executeCommand () at IOSession.Session.onMessage () at Interface.<anonymous() at () at Interface.onLine () at Interface.normalWrite () at () at () at addChunk () at readableAddChunk () at () at Pipe.onStreamRead ()
Hi , It's not a real solution, but I was able to get around this and keep working by installing the nightly build of the typescript plugin:
Thank you!
For me, the underlying crash was fixed in the latest version of vscode (1.64.0), as part of this issue:
I am still getting this issue. Including if i use the typescript extension. I am on the latest VSCode.

Version: 1.67.2 Commit: Date: 2022-05-17T18:20:57.384Z (6 days ago) Electron: 17.4.1 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 OS: Darwin x64 19.6.0 <img width="363" alt="image" src="https://user-"<img width="406" alt="image" src="https://user-"also without the extension: <img width="413" alt="image" src="https://user-"
I'm not sure how to trigger a TS server crash. If anyone who has seen this before could report if it is fixed in the latest insiders that would be great too!
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
As per my Oct 11, 2021 comment