You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the VSCode Glint plugin on our codebase, it regularly breaks down with this error:
Glint encountered an error computing diagnostics for this file. This is likely a bug in Glint; please file an issue, including any code and/or steps to follow to reproduce the error.
Error: Debug Failure. False expression: Script kind should match provided ScriptKind:1 and sourceFile.scriptKind: 3, !entry: false
at getDocumentRegistryEntry (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:142581:11)
at Object.releaseDocumentWithKey (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:142675:19)
at Object.getOrCreateSourceFileByPath [as getSourceFileByPath] (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:151555:30)
at tryReuseStructureFromOldProgram (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:126294:59)
at createProgram (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:125689:23)
at synchronizeHostDataWorker (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:151491:15)
at synchronizeHostData (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:151386:7)
at Object.getProgram (/Users/david/discourse/discourse/node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js:151568:5)
at GlintLanguageServer.isAnalyzableFile (file:///Users/david/discourse/discourse/node_modules/.pnpm/@[email protected][email protected]/node_modules/@glint/core/lib/language-server/glint-language-server.js:493:36)
at GlintLanguageServer.findDiagnosticsSource (file:///Users/david/discourse/discourse/node_modules/.pnpm/@[email protected][email protected]/node_modules/@glint/core/lib/language-server/glint-language-server.js:474:18)
We're using the stable version of Glint (1.5.2), and the officially-released Glint plugin. Typescript version 5.7.3. Our codebase is entirely .js and .gjs files - no typescript. @builtin VSCode typescript extension is disabled.
Running VSCode's "restart extension host" can resolve the issue temporarily, but then it returns as soon as you change a single character in the file. If I fully restart VSCode, then it sometimes works for a bit longer before breaking down again. I haven't been able to find a specific sequence of actions which reproduces the problem on every machine.
Does anyone have any ideas about the cause? Or a way that I can collect more information about what's happening?
The text was updated successfully, but these errors were encountered:
davidtaylorhq
changed the title
VSCode plugin: Script kind should match provided ScriptKind:1 and sourceFile.scriptKind: 3, !entry: false
VSCode plugin: Script kind should match provided ScriptKind:1Jan 28, 2025
When using the VSCode Glint plugin on our codebase, it regularly breaks down with this error:
We're using the stable version of Glint (
1.5.2
), and the officially-released Glint plugin. Typescript version 5.7.3. Our codebase is entirely.js
and.gjs
files - no typescript.@builtin
VSCode typescript extension is disabled.Running VSCode's "restart extension host" can resolve the issue temporarily, but then it returns as soon as you change a single character in the file. If I fully restart VSCode, then it sometimes works for a bit longer before breaking down again. I haven't been able to find a specific sequence of actions which reproduces the problem on every machine.
Does anyone have any ideas about the cause? Or a way that I can collect more information about what's happening?
The text was updated successfully, but these errors were encountered: