Autocomplete crashes when importing from node_modules

[MadaraUchiha]

TypeScript Version: 3.5-rc (but existed for as long as 3.0 at least)

Search Terms:
TypeScript autocomplete crashes import, Debug Failure. at Object.assertDefined getDefaultExportInfoWorker

Code
Irrelevant

Expected behavior:

Actual behavior:

TypeScript server emits an error whenever I try to import. This happens project-wide and when I open a new project under the same directory (i.e. same node_modules), autocomplete works as long as there are no imports at all in this new subproject. Any import to any package from node_modules seems to trigger it (i.e. import React from 'react';) but not imports to relative files in the project, (i.e. import { foo } from './bar';).

This is the stacktrace I get:

[2019-05-19 11:18:39.852] [exthost] [error] Error: TypeScript Server Error (3.5.0-rc)
Debug Failure.
Error: Debug Failure.
    at Object.assertDefined (tsserver.js:1558:24)
    at getDefaultExportInfoWorker (tsserver.js:115338:80)
    at getDefaultLikeExportInfo (tsserver.js:115319:24)
    at tsserver.js:115302:35
    at tsserver.js:115446:21
    at forEachExternalModule (tsserver.js:115459:21)
    at forEachExternalModuleToImportFrom (tsserver.js:115444:13)
    at getExportInfos (tsserver.js:115300:13)
    at getFixesInfoForNonUMDImport (tsserver.js:115286:57)
    at getFixesInfo (tsserver.js:115227:50)
    at Object.getCodeActions (tsserver.js:114989:28)
    at tsserver.js:112637:121
    at Object.flatMap (tsserver.js:573:25)
    at Object.getFixes (tsserver.js:112637:23)
    at tsserver.js:122213:35
    at Object.flatMap (tsserver.js:573:25)
    at Object.getCodeFixesAtPosition (tsserver.js:122211:23)
    at IOSession.Session.getCodeFixes (tsserver.js:131258:64)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:130008:61)
    at tsserver.js:131452:88
    at IOSession.Session.executeWithRequestId (tsserver.js:131443:28)
    at IOSession.Session.executeCommand (tsserver.js:131452:33)
    at IOSession.Session.onMessage (tsserver.js:131474:35)
    at Interface.<anonymous> (tsserver.js:132765:27)
    at Interface.emit (events.js:182:13)
    at Interface._onLine (readline.js:290:10)
    at Interface._normalWrite (readline.js:433:12)
    at Socket.ondata (readline.js:149:10)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:279:12)
    at readableAddChunk (_stream_readable.js:264:11)
    at Socket.Readable.push (_stream_readable.js:219:10)
    at Pipe.onread (net.js:636:20)
	at Function.create (/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension.js:1:176329)
	at v.dispatchResponse (/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension.js:1:181697)
	at v.dispatchMessage (/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension.js:1:180449)
	at constructor._reader.onData.e (/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension.js:1:179805)
	at u.fire (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:47:720)
	at t.Reader.onLengthData (/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension.js:1:185678)
	at Socket.t.Reader.constructor.e.on.e (/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension.js:1:185326)
	at Socket.emit (events.js:182:13)
	at addChunk (_stream_readable.js:279:12)
	at readableAddChunk (_stream_readable.js:264:11)
	at Socket.Readable.push (_stream_readable.js:219:10)
	at Pipe.onread (net.js:636:20)

Related Issues:
This appears to be a repeating thing: #27857 #27878 #28149

[k-eb]

I have started to see this issue too last week. I am using VSCode 1.34.0 on Windows 10 and the TypeScript version is 3.4.5.

And for me it also does not work if the type to auto-import is in the same project.

[orta]

Hi folks, I'd love to dig into this but this issue could really do with some kind of reproduction case - it looks likely related to a specific node module but without an idea of which. it's really just guess work based on the stack trace which hasn't been enough to re-create it locally..