TGlider Compatibility

TGlider works with TypeScript and JavaScript workspaces that local Node.js and TypeScript tooling can evaluate.

The TGlider package requires Node.js 24 or newer. Project support depends on project configuration, module resolution, package metadata, and the shapes TypeScript can analyze reliably.

Source Forms

Load a workspace root with the load tool before using semantic navigation, diagnostics, impact, or refactoring tools.

AreaCurrent supportNotes
.ts, .tsxSupportedPrimary TypeScript and TSX source forms, including React-style component surfaces where TypeScript can parse the file.
.js, .jsxSupportedSupported through JavaScript project settings, jsconfig.json, or inferred JS/TS projects.
.mts, .cts, .mjs, .cjsSupportedSupported where TypeScript can resolve the module mode and project ownership.
.vue, .svelteNot semantic targetsTGlider does not provide semantic intelligence inside non-TS single-file component formats unless their script content is exposed to TypeScript as ordinary JS/TS.

Project Configuration

AreaCurrent supportNotes
tsconfig.jsonSupportedIncludes project references, baseUrl, paths, skipped-config diagnostics, and project ownership detection.
jsconfig.jsonSupportedSupported for JavaScript workspaces that rely on JS project settings.
Inferred JS/TS projectsSupportedUseful for smaller workspaces without explicit config files, with less project metadata than configured projects.
Generated directoriesBest effortGenerated-looking files are filtered from some diagnostics by default; include generated files only when the workflow needs them.

Module Systems and Exports

AreaCurrent supportNotes
ESM import/exportSupportedStandard ESM exports and re-exports are part of symbol, structure, dependency, and API surface workflows.
NodeNext / Node-style resolutionSupportedTGlider follows TypeScript project settings and package type metadata where available.
TypeScript export =SupportedIncluded in export-aware tools where TypeScript can identify the exported binding.
Bounded CommonJS exportsSupported with caveatsStatic forms such as module.exports = value, exports.name = value, and module.exports.name = value are supported when the binding can be identified.
Dynamic imports and runtime export mutationUnsupportedTGlider avoids guessing dynamic runtime behavior; use explicit source inspection or runtime evidence for those cases.

Package Managers and Workspaces

AreaCurrent supportNotes
package.jsonSupportedPackage metadata, package type, scripts, dependencies, and package ownership are surfaced where available.
npm / yarn workspacesSupportedWorkspace package patterns are used for workspace package discovery.
pnpm workspace YAMLSupportedWorkspace package discovery understands pnpm workspace metadata.
Bun package-manager hintsSupportedBun package-manager metadata is detected as workspace context.
Lockfile-backed dependency graph / Yarn PnPPlannedLockfile provenance, pnpm catalogs, Yarn PnP, and richer external package graphs are roadmap items.

MCP Clients and Transports

AreaCurrent supportNotes
Claude CodeSupportedUse the Claude Code setup guide with project or user scope.
Codex CLI / IDE / AppSupportedUse Codex setup with stdio by default, or Streamable HTTP at http://localhost:5002/mcp.
Gemini CLISupportedUse the Gemini CLI setup guide with stdio MCP configuration.
CursorSupportedUse the Cursor setup guide with project or user MCP settings.
GitHub Copilot / VS CodeSupportedUse the Copilot setup guide for VS Code MCP configuration.
OpenCodeSupportedUse the OpenCode setup guide with local MCP configuration.
PiSupportedUse the Pi setup guide with pi-mcp-adapter and shared MCP config.
Stdio transportDefaultUse npx -y tglider for the simplest client-launched setup.
Streamable HTTP transportSupportedStart TGlider with tglider --transport http --port 5002; the MCP endpoint is http://localhost:5002/mcp and health is at /health.

Compatibility Notes

  • TGlider uses TypeScript compiler and language-service APIs for semantic questions before falling back to structural source evidence.
  • Support means TGlider can load and analyze the workspace through TypeScript project state. It is not a guarantee that every framework convention or generated artifact is semantically modeled.
  • When TypeScript or package metadata cannot provide stable evidence, TGlider should report unsupported or omitted shapes rather than guessing runtime behavior.
↑/↓ NavigateEnter OpenSpace Expand