complexity-report

To identify cyclomatic complexity hotspots, scan your JavaScript directories to locate functions with high CC metrics, large line counts, or deeply nested branches. This surfaces specific files and functions for targeted refactoring.

Finding refactor candidates involves running static analysis on your TypeScript code structure to report CC metrics and nesting depth. This generates a prioritized refactoring plan based on frequently executed paths and complex functions.

Yes, you can use static analysis to measure nesting depth and function size in TypeScript. It scans the code structure to report quantitative metrics, highlighting functions with large line counts and deeply nested branches as hotspots.

Complexity analysis works on both TypeScript and JavaScript source files. By default, it scans the src/ directory to apply static analysis of code structure and report cyclomatic complexity metrics across your entire project.

To generate a prioritized refactoring plan from code metrics, scan your codebase to surface hotspots based on cyclomatic complexity, line counts, and nesting depth. This outputs a targeted list of actionable refactor candidates.