Safe TypeScript & Next.js Refactoring With Tree-sitter AST Blast-Radius Guards
Text grep confuses comments, JSX strings, and local variables like `const config` with exported symbols. Real TypeScript/TSX AST parsing fixes that.
Why Regex Coupling Scans Fail in TypeScript Repos
In a typical Next.js or Express TypeScript repo, naive text search matches local variables (`const config = loadConfig()`), JSX text nodes, and import comments—flooding developers with false alarms while missing real re-exports (`export { foo }`).
Export-Aware TypeScript & TSX AST Auditing
Kronumos uses native `tree-sitter-typescript` and TSX grammars to distinguish exported types, functions, and CommonJS exports from module-local variables. Running `kronumos blast` maps exact cross-file caller counts in milliseconds, and Auto Blast-Radius Guard injects impacted caller files automatically before an agent mutates shared symbols.
# Map top exported coupled symbols across your TypeScript workspace
kronumos blast
# Inspect callers for one specific symbol before editing its signature
kronumos blast createApp“Export-aware Tree-sitter AST parsing eliminates grep noise and keeps AI refactoring safe across TypeScript and Next.js codebases.”
Frequently Asked Questions
Does Kronumos support both .ts and .tsx React files?
Yes. Kronumos bundles separate Tree-sitter TypeScript and TSX grammars so JSX tags are distinguished from string attributes and text nodes.
Audit your repository in milliseconds with zero LLM calls
Run native Rust Tree-sitter AST checks on Linux, macOS, and Windows PowerShell, or test in the browser.