CODE ANALYZER CLI

Advanced code analysis CLI for memory leaks and performance issues.

Overview

This CLI tool provides sophisticated analysis capabilities for JavaScript/TypeScript projects:

1. Memory Monitoring: Track memory usage patterns to detect potential memory leaks
2. Code Pattern Analysis: Scan codebase for common memory leak patterns

Installation

# Install dependencies
bun install

# Run in development mode
bun run dev

# Build for production
bun run build

Usage

Interactive mode (default)

Running the CLI with no arguments launches interactive mode, which guides you through options with prompts:

analyzer
# or explicitly:
analyzer -i

You can choose to run memory monitoring or code analysis, then set options (interval, measurements, directory, save report, etc.) via prompts.

Global options

• -i, --interactive — Launch interactive mode
• --no-color — Disable colored output (for CI/pipes)
• -v, --verbose — Verbose output
• -q, --quiet — Minimal output
• -V, --version — Show version (from package.json)
• -h, --help — Show help

Memory Monitoring

Monitor memory usage and detect potential memory leaks:

analyzer memory [options]

Options:

• -i, --interval <ms>: Interval between measurements in milliseconds (default: 2000)
• -m, --measurements <count>: Number of measurements to take (default: 20)
• -g, --gc: Force garbage collection before each measurement (requires --expose-gc)
• -p, --process <name>: Name of the process being monitored (default: "Node.js Process")
• -s, --save: Save detailed report to file

Example:

analyzer memory --interval 1000 --measurements 30 --gc

Code Pattern Analysis

Analyze code for memory leak patterns:

analyzer code [directory] [options]

Options:

• -s, --save: Save detailed report to file
• -q, --quick: Run quick scan for critical issues only

Example:

analyzer code ./src --save

Features

Memory Monitoring

• Real-time memory usage tracking
• Leak detection algorithms
• GC efficiency analysis
• Memory pressure indicators
• Detailed recommendations

Code Pattern Analysis

• Detection of common memory leak patterns:
  • Event listener leaks
  • Timer/interval leaks
  • React useEffect cleanup issues
  • Global object issues
  • Closure leaks
  • State mutation issues
  • Missing dependencies
  • Infinite render patterns
  • DOM reference issues