nested-complexity-hotspots

📡 Live from GitHub — This documentation is fetched directly from nested-complexity-hotspots.md and cached for 6 hours.

Keywords: nested complexity hotspots, complexity, ESLint rule, JavaScript, TypeScript

ESLint Rule: nested-complexity-hotspots with LLM-optimized suggestions and auto-fix capabilities.

Quick Summary

Aspect	Details
Severity	Error (code quality)
Auto-Fix	❌ No
Category	Quality
ESLint MCP	✅ Optimized for ESLint MCP integration
Best For	Production applications
Suggestions	✅ 4 available

No configuration options available.

// Example of incorrect usage

// Example of correct usage

// eslint.config.mjs
export default [
  {
    rules: {
      'maintainability/nested-complexity-hotspots': 'error',
    },
  },
];

🚨 nested complexity hotspots | Description | MEDIUM
   Fix: Suggestion | Reference

The following patterns are not detected due to static analysis limitations:

Why: Static analysis cannot trace values stored in variables or passed through function parameters.

// ❌ NOT DETECTED - Value from variable
const value = externalSource();
processValue(value); // Variable origin not tracked

Mitigation: Implement runtime validation and review code manually. Consider using TypeScript branded types for validated inputs.

Why: When values come from imports, the rule cannot analyze their origin or construction.

// ❌ NOT DETECTED - Value from import
import { getValue } from './helpers';
processValue(getValue()); // Cross-file not tracked

Mitigation: Ensure imported values follow the same constraints. Use TypeScript for type safety.