TypeScript graph

A CLI to visualize the dependencies between files in the TypeScript codebase.

For example, the following command in the base directory of https://github.com/ysk8hori/numberplace will produce the following results:

``bash tsg src/components/atoms/ConfigMenu --exclude test stories node_modules`

`mermaid flowchart classDef dir fill:#0000,stroke:#999 subgraph src["src"] src/atoms.ts["atoms.ts"] subgraph src/components/atoms["/components/atoms"] src/components/atoms/Button.tsx["Button.tsx"] subgraph src/components/atoms/ConfigMenu["/ConfigMenu"] src/components/atoms/ConfigMenu/index.tsx["index.tsx"] subgraph src/components/atoms/ConfigMenu/MenuStack["/MenuStack"] src/components/atoms/ConfigMenu/MenuStack/MenuStack.tsx["MenuStack.tsx"] src/components/atoms/ConfigMenu/MenuStack/index.ts["index.ts"] end subgraph src/components/atoms/ConfigMenu/MenuButton["/MenuButton"] src/components/atoms/ConfigMenu/MenuButton/MenuButton.tsx["MenuButton.tsx"] src/components/atoms/ConfigMenu/MenuButton/index.ts["index.ts"] end end end subgraph src/pages["/pages"] subgraph src/pages/GameContainer["/GameContainer"] src/pages/GameContainer/GameContainer.tsx["GameContainer.tsx"] end subgraph src/pages/GenerateGameContainer["/GenerateGameContainer"] src/pages/GenerateGameContainer/GenerateGameContainer.tsx["GenerateGameContainer.tsx"] end subgraph src/pages/StartMenu["/StartMenu"] src/pages/StartMenu/StartMenu.tsx["StartMenu.tsx"] end end end src/components/atoms/ConfigMenu/MenuStack/MenuStack.tsx-->src/atoms.ts src/components/atoms/ConfigMenu/MenuStack/MenuStack.tsx-->src/components/atoms/Button.tsx src/components/atoms/ConfigMenu/MenuStack/index.ts-->src/components/atoms/ConfigMenu/MenuStack/MenuStack.tsx src/components/atoms/ConfigMenu/MenuButton/MenuButton.tsx-->src/components/atoms/Button.tsx src/components/atoms/ConfigMenu/index.tsx-->src/components/atoms/ConfigMenu/MenuStack/index.ts src/components/atoms/ConfigMenu/index.tsx-->src/components/atoms/ConfigMenu/MenuButton/MenuButton.tsx src/pages/GameContainer/GameContainer.tsx-->src/components/atoms/ConfigMenu/index.tsx src/pages/GenerateGameContainer/GenerateGameContainer.tsx-->src/components/atoms/ConfigMenu/index.tsx src/pages/StartMenu/StartMenu.tsx-->src/components/atoms/ConfigMenu/index.tsx src/components/atoms/ConfigMenu/MenuButton/index.ts-->src/components/atoms/ConfigMenu/MenuButton/MenuButton.tsx`

`Installation`

`bash npm install --global @ysk8hori/typescript-graph`

`Arguments`

| Argument | Description | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------- | |include-files | Specify file paths or parts of file paths to include in the graph (relative to the tsconfig directory, without ./). (default: "") |

`Options`

| Option | Description | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |-V, --version| Output the version number | |--md | Specify the name of the markdown file to be output. The default is typescript-graph.md. | |-d, --dir | Specifies the root directory of the TypeScript project to analyze. It reads and uses the tsconfig.json file found in this directory. | |--tsconfig | Specifies the path to the tsconfig file to use for analysis. If this option is provided, -d, --dir will be ignored. | |--include | Specify file paths or parts of file paths to include in the graph (relative to the tsconfig directory, without ./). | |--exclude | Specify file paths or parts of file paths to exclude from the graph (relative to the tsconfig directory, without ./). | |--abstraction | Specify the paths of directories to be abstracted. Abstracted directories are treated as a single node. | |--highlight | Specify the path and file names to be highlighted. | |--LR| Set the flowchart orientation to Left-to-Right. | |--TB| Set the flowchart orientation to Top-to-Bottom. | |--measure-instability| Enable the beta feature to measure the instability of modules. | |--metrics| Enables a beta feature to measure code metrics such as Maintainability Index, Cyclomatic Complexity, and Cognitive Complexity. This can be used as an analytical tool to quantitatively evaluate code quality. | |-w, --watch-metrics| Monitors file changes in real-time and displays metrics such as Maintainability Index, Cyclomatic Complexity, and Cognitive Complexity whenever changes occur. Ideal for continuous quality monitoring. | |--config-file| Specify the relative path to the config file (from the current directory or as specified by -d, --dir). The default is .tsgrc.json. | |--vue (experimental) | .vue files are also included in the analysis. A temporary working directory is created using Node.js's fs.mkdtempSync, where all files targeted by tsc as well as .vue files are copied for processing. .vue files are renamed to .vue.tsunless a file with the same name already exists in the directory. | |--stdout [types...] | Output structured data to stdout. Types: metrics, deps, or omit for all (default: all). Examples: --stdout (all), --stdout metrics (metrics only), --stdout deps (dependency graph only), --stdout metrics deps(both) | |-h, --help | Display help for the command. |

`usage`

Run tsg on the project you want to analyze.

`bash tsg`

`mermaid flowchart classDef dir fill:#0000,stroke:#999 subgraph src["src"] src/utils.ts["utils.ts"] src/config.ts["config.ts"] src/main.ts["main.ts"] subgraph src/includeFiles["/includeFiles"] src/includeFiles/b.ts["b.ts"] src/includeFiles/c.ts["c.ts"] src/includeFiles/a.ts["a.ts"] subgraph src/includeFiles/children["/children"] src/includeFiles/children/childA.ts["childA.ts"] end subgraph src/includeFiles/excludeFiles["/excludeFiles"] src/includeFiles/excludeFiles/g.ts["g.ts"] src/includeFiles/excludeFiles/i.ts["i.ts"] src/includeFiles/excludeFiles/h.ts["h.ts"] end subgraph src/includeFiles/abstractions["/abstractions"] src/includeFiles/abstractions/j.ts["j.ts"] src/includeFiles/abstractions/l.ts["l.ts"] src/includeFiles/abstractions/k.ts["k.ts"] subgraph src/includeFiles/abstractions/children["/children"] src/includeFiles/abstractions/children/childA.ts["childA.ts"] end end end subgraph src/otherFiles["/otherFiles"] src/otherFiles/d.ts["d.ts"] src/otherFiles/f.ts["f.ts"] src/otherFiles/e.ts["e.ts"] subgraph src/otherFiles/children["/children"] src/otherFiles/children/childA.ts["childA.ts"] end end end src/includeFiles/b.ts-->src/utils.ts src/includeFiles/b.ts-->src/config.ts src/includeFiles/c.ts-->src/utils.ts src/includeFiles/c.ts-->src/includeFiles/b.ts src/config.ts-->src/utils.ts src/config.ts-->src/includeFiles/c.ts src/includeFiles/children/childA.ts-->src/utils.ts src/includeFiles/excludeFiles/g.ts-->src/includeFiles/children/childA.ts src/includeFiles/excludeFiles/g.ts-->src/utils.ts src/includeFiles/excludeFiles/i.ts-->src/utils.ts src/includeFiles/excludeFiles/h.ts-->src/includeFiles/excludeFiles/i.ts src/includeFiles/excludeFiles/h.ts-->src/utils.ts src/includeFiles/excludeFiles/h.ts-->src/config.ts src/includeFiles/a.ts-->src/includeFiles/children/childA.ts src/includeFiles/a.ts-->src/includeFiles/excludeFiles/g.ts src/includeFiles/a.ts-->src/includeFiles/excludeFiles/h.ts src/includeFiles/a.ts-->src/includeFiles/excludeFiles/i.ts src/includeFiles/a.ts-->src/utils.ts src/otherFiles/children/childA.ts-->src/utils.ts src/otherFiles/d.ts-->src/otherFiles/children/childA.ts src/otherFiles/d.ts-->src/utils.ts src/otherFiles/f.ts-->src/utils.ts src/otherFiles/e.ts-->src/otherFiles/f.ts src/otherFiles/e.ts-->src/utils.ts src/otherFiles/e.ts-->src/config.ts src/includeFiles/abstractions/j.ts-->src/utils.ts src/includeFiles/abstractions/j.ts-->src/includeFiles/abstractions/children/childA.ts src/includeFiles/abstractions/l.ts-->src/utils.ts src/includeFiles/abstractions/k.ts-->src/includeFiles/abstractions/l.ts src/includeFiles/abstractions/k.ts-->src/utils.ts src/main.ts-->src/includeFiles/a.ts src/main.ts-->src/includeFiles/b.ts src/main.ts-->src/otherFiles/d.ts src/main.ts-->src/otherFiles/e.ts src/main.ts-->src/includeFiles/abstractions/j.ts src/main.ts-->src/includeFiles/abstractions/k.ts src/main.ts-->src/utils.ts`

👆 and outputs file dependencies.

It is cluttered and confusing. Also, for large repositories, Mermaid may exceed the maximum amount of data that can be displayed.

In that case, you need to narrow down the directories to include in the graph.

`$3`

To narrow down the directories or files included in the graph, specify the paths or parts of the paths using either the argument or the --include option.

`bash tsg src/includeFiles config`

`mermaid flowchart classDef dir fill:#0000,stroke:#999 subgraph src["src"] src/config.ts["config.ts"] src/utils.ts["utils.ts"] src/main.ts["main.ts"] subgraph src/includeFiles["/includeFiles"] src/includeFiles/b.ts["b.ts"] src/includeFiles/c.ts["c.ts"] src/includeFiles/a.ts["a.ts"] subgraph src/includeFiles/children["/children"] src/includeFiles/children/childA.ts["childA.ts"] end subgraph src/includeFiles/excludeFiles["/excludeFiles"] src/includeFiles/excludeFiles/g.ts["g.ts"] src/includeFiles/excludeFiles/i.ts["i.ts"] src/includeFiles/excludeFiles/h.ts["h.ts"] end subgraph src/includeFiles/abstractions["/abstractions"] src/includeFiles/abstractions/j.ts["j.ts"] src/includeFiles/abstractions/l.ts["l.ts"] src/includeFiles/abstractions/k.ts["k.ts"] subgraph src/includeFiles/abstractions/children["/children"] src/includeFiles/abstractions/children/childA.ts["childA.ts"] end end end subgraph src/otherFiles["/otherFiles"] src/otherFiles/e.ts["e.ts"] end end src/includeFiles/b.ts-->src/utils.ts src/includeFiles/b.ts-->src/config.ts src/includeFiles/c.ts-->src/utils.ts src/includeFiles/c.ts-->src/includeFiles/b.ts src/config.ts-->src/utils.ts src/config.ts-->src/includeFiles/c.ts src/includeFiles/children/childA.ts-->src/utils.ts src/includeFiles/excludeFiles/g.ts-->src/includeFiles/children/childA.ts src/includeFiles/excludeFiles/g.ts-->src/utils.ts src/includeFiles/excludeFiles/i.ts-->src/utils.ts src/includeFiles/excludeFiles/h.ts-->src/includeFiles/excludeFiles/i.ts src/includeFiles/excludeFiles/h.ts-->src/utils.ts src/includeFiles/excludeFiles/h.ts-->src/config.ts src/includeFiles/a.ts-->src/includeFiles/children/childA.ts src/includeFiles/a.ts-->src/includeFiles/excludeFiles/g.ts src/includeFiles/a.ts-->src/includeFiles/excludeFiles/h.ts src/includeFiles/a.ts-->src/includeFiles/excludeFiles/i.ts src/includeFiles/a.ts-->src/utils.ts src/otherFiles/e.ts-->src/config.ts src/includeFiles/abstractions/j.ts-->src/utils.ts src/includeFiles/abstractions/j.ts-->src/includeFiles/abstractions/children/childA.ts src/includeFiles/abstractions/l.ts-->src/utils.ts src/includeFiles/abstractions/k.ts-->src/includeFiles/abstractions/l.ts src/includeFiles/abstractions/k.ts-->src/utils.ts src/main.ts-->src/includeFiles/a.ts src/main.ts-->src/includeFiles/b.ts src/main.ts-->src/includeFiles/abstractions/j.ts src/main.ts-->src/includeFiles/abstractions/k.ts`

As mentioned above, only the dependencies of the directories specified by the argument or the --include option will be output. However, the dependencies of the files under the specified directories will still be displayed. If there are directories or files you are not interested in, use the --exclude option to exclude them.

#### Exclude Exception via Full Path Specification (Experimental)

There might be scenarios where you would want to ignore dependency relations for a certain folder using exclude, but within that folder, there may exist some files you wish to include in the graph. In such cases, you can exclude a specific file from the exclusion list by specifying its full path in the argument or with the --include option.

`$3`

Directories and files to be excluded from the graph are excluded with the --exclude option.

`bash tsg includeFiles config --exclude excludeFiles utils`

`mermaid flowchart classDef dir fill:#0000,stroke:#999 subgraph src["src"] src/config.ts["config.ts"] src/main.ts["main.ts"] subgraph src/includeFiles["/includeFiles"] src/includeFiles/b.ts["b.ts"] src/includeFiles/c.ts["c.ts"] src/includeFiles/a.ts["a.ts"] subgraph src/includeFiles/children["/children"] src/includeFiles/children/childA.ts["childA.ts"] end subgraph src/includeFiles/abstractions["/abstractions"] src/includeFiles/abstractions/j.ts["j.ts"] src/includeFiles/abstractions/l.ts["l.ts"] src/includeFiles/abstractions/k.ts["k.ts"] subgraph src/includeFiles/abstractions/children["/children"] src/includeFiles/abstractions/children/childA.ts["childA.ts"] end end end subgraph src/otherFiles["/otherFiles"] src/otherFiles/e.ts["e.ts"] end end src/includeFiles/b.ts-->src/config.ts src/includeFiles/c.ts-->src/includeFiles/b.ts src/config.ts-->src/includeFiles/c.ts src/includeFiles/a.ts-->src/includeFiles/children/childA.ts src/otherFiles/e.ts-->src/config.ts src/includeFiles/abstractions/j.ts-->src/includeFiles/abstractions/children/childA.ts src/includeFiles/abstractions/k.ts-->src/includeFiles/abstractions/l.ts src/main.ts-->src/includeFiles/a.ts src/main.ts-->src/includeFiles/b.ts src/main.ts-->src/includeFiles/abstractions/j.ts src/main.ts-->src/includeFiles/abstractions/k.ts`

The directories specified with --exclude were excluded from the dependency graph.

Oops, src/includeFiles/b.ts, src/includeFiles/c.ts and src/config.ts were circular references. Report this immediately to your team for refactoring. However, src/includeFiles/abstractions has nothing to do with this issue, so we don't want to show them the details if possible. You can hide the details of src/includeFiles/abstractions with --abstraction.

`$3`

Sometimes you may not be interested in the files in a directory, but wish to keep the dependencies on that directory in the graph. In such cases, use--abstraction to abstract the directory.

`bash tsg includeFiles config --exclude excludeFiles utils --abstraction abstractions`

This makes it easier to share problems within the team👍.

However, I would like to emphasize what I would like to see emphasized 🤔.

`$3`

Use --highlight to highlight nodes that need attention.

`bash tsg includeFiles config --exclude excludeFiles utils --abstraction abstractions --highlight config.ts b.ts --LR`

`mermaid flowchart LR classDef dir fill:#0000,stroke:#999 classDef highlight fill:yellow,color:black subgraph src["src"] src/config.ts["config.ts"]:::highlight src/main.ts["main.ts"] subgraph src/includeFiles["/includeFiles"] src/includeFiles/b.ts["b.ts"]:::highlight src/includeFiles/c.ts["c.ts"] src/includeFiles/a.ts["a.ts"] src/includeFiles/abstractions["/abstractions"]:::dir subgraph src/includeFiles/children["/children"] src/includeFiles/children/childA.ts["childA.ts"] end end subgraph src/otherFiles["/otherFiles"] src/otherFiles/e.ts["e.ts"] end end src/includeFiles/b.ts-->src/config.ts src/includeFiles/c.ts-->src/includeFiles/b.ts src/config.ts-->src/includeFiles/c.ts src/includeFiles/a.ts-->src/includeFiles/children/childA.ts src/otherFiles/e.ts-->src/config.ts src/includeFiles/abstractions-->data.json src/main.ts-->src/includeFiles/a.ts src/main.ts-->src/includeFiles/b.ts src/main.ts-->src/includeFiles/abstractions`

It makes it easier to share problems within the team. 👍

`$3`

When using TypeScript Graph with AI agents, the --stdout option provides structured output that's easy to parse and analyze:

`bash

`Analyze codebase architecture and get both dependency graph and metrics`


tsg --stdout
Get only code metrics for quality assessment

tsg --stdout metrics
Get only dependency relationships for architecture analysis

tsg --stdout deps


Example prompts for AI agents:

`Analyze this TypeScript codebase architecture: $(tsg --stdout deps)

Identify circular dependencies and suggest refactoring strategies.`

`Review code quality metrics: $(tsg --stdout metrics)

Identify files with low maintainability index and high complexity that need refactoring.`

`Full codebase analysis: $(tsg --stdout)

Provide architectural insights and code quality recommendations.`

`Review code quality for changes in the current branch: $(tsg --stdout --include $(git diff --name-only main | tr '\n' ' '))`

`Code Metrics Measurement`

This is a beta feature for measuring code metrics such as the Maintainability Index, Cyclomatic Complexity, and Cognitive Complexity. While these metrics are widely recognized, their reliability in TypeScript-specific contexts is not guaranteed. Nonetheless, they can serve as helpful indicators for evaluating code quality.

For example, navigate to typescript-graph/dummy_project_for_metrics and execute the following command:

`bash tsg --metrics`

In addition to the usual content of typescript-graph.md, metrics like the following will be output:

---

file	scope	name	Maintainability Index	Cyclomatic Complexity	Cognitive Complexity	lines	semantic syntax volume	total operands	unique operands	total semantic syntax	unique semantic syntax
badCode.ts	file	-	28.54	27	351	111	1807.98	107	55	190	13
badCode.ts	function	badCode	💥 7.23	27	351	110	1814.06	107	55	191	13
goodCode.ts	file	-	82.21	2	1	4	77.66	6	4	13	13
goodCode.ts	function	goodCode	76	2	1	3	81.75	6	4	14	13

CSV

`csv file,scope,name,Maintainability Index,Cyclomatic Complexity,Cognitive Complexity,lines,semantic syntax volume,total operands,unique operands,total semantic syntax,unique semantic syntax badCode.ts,file,-,28.540438644839494,27,351,111,1807.9764638513507,107,55,190,13 badCode.ts,function,badCode,7.2309524830767815,27,351,110,1814.063926692601,107,55,191,13 goodCode.ts,file,-,82.20502409726409,2,1,4,77.66179398375644,6,4,13,13 goodCode.ts,function,goodCode,75.99910291534641,2,1,3,81.74925682500678,6,4,14,13`

TSV

`tsv file scope name Maintainability Index Cyclomatic Complexity Cognitive Complexity lines semantic syntax volume total operands unique operands total semantic syntax unique semantic syntax badCode.ts file - 28.540438644839494 27 351 111 1807.9764638513507 107 55 190 13 badCode.ts function badCode 7.2309524830767815 27 351 110 1814.063926692601 107 55 191 13 goodCode.ts file - 82.20502409726409 2 1 4 77.66179398375644 6 4 13 13 goodCode.ts function goodCode 75.99910291534641 2 1 3 81.74925682500678 6 4 14 13`

---

`$3`

This metric calculates an index value ranging from 0 to 100, representing the relative ease of maintaining the code. Higher values indicate better maintainability. Two thresholds are defined, and an icon is displayed if the index falls below them. Since this is a beta feature, the formulas and thresholds may change.

| threshold | state | icon | | --------- | -------- | ---- | | 20 | alert | 🧨 | | 10 | critical | 💥 |

Future updates may introduce customizations for formulas and thresholds.

`$3`

Cyclomatic Complexity in TypeScript Graph includes Conditional Types. For additional information, a web search will provide more precise details than this document.

`$3`

In simple terms, Cognitive Complexity is similar to Cyclomatic Complexity in that it scores based on control flow branches. However, it imposes penalties for nested control structures.

This implementation is based on the whitepaper “A new way of measuring understandability” by G. Ann Campbell from SonarSource. Note that this project is not affiliated with SonarSource.

Currently, the implementation does not fully account for TypeScript's type system. We acknowledge the need for improvements and may address this in future updates.

#### Differences from SonarSource's Cognitive Complexity

The handling of functions assigned to objects as substitutes for classes differs. SonarSource only increments nesting levels when the structure is non-declarative. In contrast, TypeScript Graph increments nesting levels without considering whether the structure is declarative.

`$3`

The Maintainability Index calculation typically uses the Halstead Volume metric, which is derived from the total and unique counts of operators and operands in the source code.

In TypeScript Graph, the number of non-operand nodes in the AST (after excluding nodes deemed irrelevant for counting) is used as a substitute, as counting operators directly from the AST can be cumbersome.

The calculation formula is as follows:

`typescript function volume(): number { const N = totalSemanticSyntax.count + totalOperands.count; const n = uniqueSemanticSyntax.count + uniqueOperands.count; return N * Math.log2(n); }`

`$3`

You can monitor file changes in real time and display metrics such as the Maintainability Index, Cyclomatic Complexity, and Cognitive Complexity whenever changes occur using the following command:

`bash tsg --watch-metrics`

!tsg --watch-metrics result

The values in () represent the difference from when monitoring started. Improvements are displayed in green, while regressions are shown in red. Whether an increase or decrease is better depends on the metric. The following table outlines the preferred directions for each metric:

| Metrics Name | Better Direction | | --------------------- | ---------------- | | Maintainability Index | Higher | | Cyclomatic Complexity | Lower | | Cognitive Complexity | Lower |

`stdout Output`

The --stdoutoption outputs a machine-parsable format that can include architectural structure and/or code complexity metrics. It’s designed for AI agents like Claude Code or GitHub Copilot Agent, as well as humans who prefer structured command-line output.

`$3`

`bash

`Output both dependency graph and metrics (default)`


tsg --stdout
Output only metrics

tsg --stdout metrics
Output only dependency graph

tsg --stdout deps
Output both (explicit)

tsg --stdout metrics deps


This can produce one or both of these clearly separated sections:

1. Dependency Graph (Mermaid) - Available with depsA visual graph of file dependencies, useful for detecting circular references and architectural patterns.

2. Code Metrics (JSON) - Available with metricsA machine-readable summary of key maintainability indicators for each file.

Example output with --stdout (both sections):

`=== DEPENDENCY GRAPH === flowchart [dependency relationships in Mermaid syntax]

=== CODE METRICS === { "metrics": [ { "filePath": "src/utils.ts", "maintainabilityIndex": 95.75, "cyclomaticComplexity": 1, "cognitiveComplexity": 0 } ] }`

Example output with --stdout metrics (metrics only):

`=== CODE METRICS === { "metrics": [...] }`

Example output with --stdout deps (dependency graph only):

`=== DEPENDENCY GRAPH === flowchart [dependency relationships in Mermaid syntax]``

$3

- Human-friendly + machine-friendly
Easily piped into LLM agents, static analyzers, or documentation tools. Humans can read it too.

- Mermaid for structure
Enables visual recognition of circular dependencies, hub files, and architectural boundaries.

- JSON for metrics
Clean structure for parsing, threshold checking, or automated prioritization.

- Focused indicators
Only the three most relevant metrics:

- Maintainability Index
- Cyclomatic Complexity
- Cognitive Complexity

TypeScript graph

English •
日本語 (Japanese)

A CLI to visualize the dependencies between files in the TypeScript codebase.

For example, the following command in the base directory of https://github.com/ysk8hori/numberplace will produce the following results:

``bash tsg src/components/atoms/ConfigMenu --exclude test stories node_modules`

`Installation`

`bash npm install --global @ysk8hori/typescript-graph`

`Arguments`

`Options`

`usage`

Run tsg on the project you want to analyze.

`bash tsg`

👆 and outputs file dependencies.

It is cluttered and confusing. Also, for large repositories, Mermaid may exceed the maximum amount of data that can be displayed.

In that case, you need to narrow down the directories to include in the graph.

`$3`

To narrow down the directories or files included in the graph, specify the paths or parts of the paths using either the argument or the --include option.

`bash tsg src/includeFiles config`

#### Exclude Exception via Full Path Specification (Experimental)

`$3`

Directories and files to be excluded from the graph are excluded with the --exclude option.

`bash tsg includeFiles config --exclude excludeFiles utils`

The directories specified with --exclude were excluded from the dependency graph.

`$3`

Sometimes you may not be interested in the files in a directory, but wish to keep the dependencies on that directory in the graph. In such cases, use--abstraction to abstract the directory.

`bash tsg includeFiles config --exclude excludeFiles utils --abstraction abstractions`

This makes it easier to share problems within the team👍.

However, I would like to emphasize what I would like to see emphasized 🤔.

`$3`

Use --highlight to highlight nodes that need attention.

`bash tsg includeFiles config --exclude excludeFiles utils --abstraction abstractions --highlight config.ts b.ts --LR`

It makes it easier to share problems within the team. 👍

`$3`

When using TypeScript Graph with AI agents, the --stdout option provides structured output that's easy to parse and analyze:

`bash

`Analyze codebase architecture and get both dependency graph and metrics`


tsg --stdout
Get only code metrics for quality assessment

tsg --stdout metrics
Get only dependency relationships for architecture analysis

tsg --stdout deps


Example prompts for AI agents:

`Analyze this TypeScript codebase architecture: $(tsg --stdout deps)

Identify circular dependencies and suggest refactoring strategies.`

`Review code quality metrics: $(tsg --stdout metrics)

Identify files with low maintainability index and high complexity that need refactoring.`

`Full codebase analysis: $(tsg --stdout)

Provide architectural insights and code quality recommendations.`

`Review code quality for changes in the current branch: $(tsg --stdout --include $(git diff --name-only main | tr '\n' ' '))`

`Code Metrics Measurement`

For example, navigate to typescript-graph/dummy_project_for_metrics and execute the following command:

`bash tsg --metrics`

In addition to the usual content of typescript-graph.md, metrics like the following will be output:

---

file	scope	name	Maintainability Index	Cyclomatic Complexity	Cognitive Complexity	lines	semantic syntax volume	total operands	unique operands	total semantic syntax	unique semantic syntax
badCode.ts	file	-	28.54	27	351	111	1807.98	107	55	190	13
badCode.ts	function	badCode	💥 7.23	27	351	110	1814.06	107	55	191	13
goodCode.ts	file	-	82.21	2	1	4	77.66	6	4	13	13
goodCode.ts	function	goodCode	76	2	1	3	81.75	6	4	14	13

CSV

TSV

---

`$3`

| threshold | state | icon | | --------- | -------- | ---- | | 20 | alert | 🧨 | | 10 | critical | 💥 |

Future updates may introduce customizations for formulas and thresholds.

`$3`

Cyclomatic Complexity in TypeScript Graph includes Conditional Types. For additional information, a web search will provide more precise details than this document.

`$3`

In simple terms, Cognitive Complexity is similar to Cyclomatic Complexity in that it scores based on control flow branches. However, it imposes penalties for nested control structures.

This implementation is based on the whitepaper “A new way of measuring understandability” by G. Ann Campbell from SonarSource. Note that this project is not affiliated with SonarSource.

Currently, the implementation does not fully account for TypeScript's type system. We acknowledge the need for improvements and may address this in future updates.

#### Differences from SonarSource's Cognitive Complexity

`$3`

The Maintainability Index calculation typically uses the Halstead Volume metric, which is derived from the total and unique counts of operators and operands in the source code.

The calculation formula is as follows:

`typescript function volume(): number { const N = totalSemanticSyntax.count + totalOperands.count; const n = uniqueSemanticSyntax.count + uniqueOperands.count; return N * Math.log2(n); }`

`$3`

You can monitor file changes in real time and display metrics such as the Maintainability Index, Cyclomatic Complexity, and Cognitive Complexity whenever changes occur using the following command:

`bash tsg --watch-metrics`

!tsg --watch-metrics result

| Metrics Name | Better Direction | | --------------------- | ---------------- | | Maintainability Index | Higher | | Cyclomatic Complexity | Lower | | Cognitive Complexity | Lower |

`stdout Output`

`$3`

`bash

`Output both dependency graph and metrics (default)`


tsg --stdout
Output only metrics

tsg --stdout metrics
Output only dependency graph

tsg --stdout deps
Output both (explicit)

tsg --stdout metrics deps


This can produce one or both of these clearly separated sections:

1. Dependency Graph (Mermaid) - Available with depsA visual graph of file dependencies, useful for detecting circular references and architectural patterns.

2. Code Metrics (JSON) - Available with metricsA machine-readable summary of key maintainability indicators for each file.

Example output with --stdout (both sections):

`=== DEPENDENCY GRAPH === flowchart [dependency relationships in Mermaid syntax]

=== CODE METRICS === { "metrics": [ { "filePath": "src/utils.ts", "maintainabilityIndex": 95.75, "cyclomaticComplexity": 1, "cognitiveComplexity": 0 } ] }`

Example output with --stdout metrics (metrics only):

`=== CODE METRICS === { "metrics": [...] }`

Example output with --stdout deps (dependency graph only):

`=== DEPENDENCY GRAPH === flowchart [dependency relationships in Mermaid syntax]``

$3

- Human-friendly + machine-friendly
Easily piped into LLM agents, static analyzers, or documentation tools. Humans can read it too.

- Mermaid for structure
Enables visual recognition of circular dependencies, hub files, and architectural boundaries.

- JSON for metrics
Clean structure for parsing, threshold checking, or automated prioritization.

- Focused indicators
Only the three most relevant metrics:

- Maintainability Index
- Cyclomatic Complexity
- Cognitive Complexity