Tool selection guide
When TypeScript semantic tools help
Choose tools for TypeScript and JavaScript projects, symbols, diagnostics, dependencies, and edits.
Choose a task
Orient in a workspace
Identify projects, packages, configuration, and ownership before editing.
- Workspace tools report the loaded project contexts.
- Package and module context can distinguish similar files in different projects.
Resolve symbols and exports
Find declarations, references, implementations, and public API surfaces.
- Symbol results carry reusable keys and source spans.
- Export tools distinguish a project API from a local name match.
Inspect diagnostics and calls
Read diagnostics, callers, outgoing calls, and bounded impact.
- Diagnostic results can be filtered and grouped.
- Call and impact tools start from semantic symbol identity.
Map dependencies
Inspect project and file relationships before an architecture change.
- Dependency tools return project and file ownership with graph edges.
- Module-resolution evidence explains how a specific import resolves.
Analyze live documents
Keep semantic reads aligned with unsaved document text.
- Open documents have explicit versions.
- Diagnostics and navigation can use the in-memory document state.
Preview a rename or edit
Compute changes before writing them to the workspace.
- Use compute_rename_edits for a rename plan. rename_symbol applies it to live documents. Preview each write_file save, then apply with its disk fingerprint and the current document version.
- Check each edit tool’s defaults. Inspect diagnostics after application.
Scope and related tools
- TGlider analyzes TypeScript and JavaScript project state. It has no text-search tool.
- Use Scout for repository text and other languages. Run builds and tests through your project scripts.