Skip TypeScript activation and patching for GJS/GTS projects without tsconfig/jsconfig

[Copilot]

JS/GJS projects without a tsconfig.json or jsconfig.json were receiving spurious TypeScript errors (ts-plugin(1128): Declaration or statement expected) because the extension unconditionally patched the TS extension to treat .gjs/.gts as TypeScript-like languages — causing the raw TS parser to choke on <template> syntax with no Glint server running to handle it.

Changes (packages/vscode/src/extension.ts)

• TS extension activation — gate tsExtension.activate() behind hasWorkspaceConfig so TypeScript never activates for config-less GJS projects
• TS extension patching — gate the jsTsLanguageModes / isSupportedLanguageMode monkey-patch behind the same hasWorkspaceConfig check, preventing .gjs/.gts from being registered as TS-like language modes
• configureTsserverPlugin — early-return when no config file is found, eliminating the noise log lines (typescript.configurePlugin not available, Workspace ember-tsc not found) that appeared even when Glint had already correctly skipped activation

const patchWorkspaceRoot = vscode.workspace.workspaceFolders?.[0]?.uri.fsPath;
const hasWorkspaceConfig = patchWorkspaceRoot
  ? !!findConfigFileInWorkspace(patchWorkspaceRoot)
  : false;

if (tsExtension && hasWorkspaceConfig) { /* activate */ }
if (!v1ExtensionPresent && hasWorkspaceConfig) { /* patch */ }

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[ef4]

Is this superseded?

[NullVoxPopuli]

yup