Biome Strict Linting Rules

CLAUDE.md Content

The main content for this claude.md.

biome-strict-linting-rules.json

json

{
  "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json",
  "formatter": {
    "enabled": true,
    "indentStyle": "tab",
    "indentWidth": 2,
    "lineWidth": 100,
    "lineEnding": "lf"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error",
        "noUnusedImports": "error",
        "noUndeclaredVariables": "error",
        "noConstAssign": "error"
      },
      "suspicious": {
        "noDebugger": "error",
        "noConsoleLog": "warn",
        "noDoubleEquals": "error",
        "noRedundantUseStrict": "warn"
      },
      "complexity": {
        "noStaticOnlyClass": "warn",
        "noUselessEmptyExport": "error"
      },
      "style": {
        "noVar": "error",
        "useConst": "error",
        "useTemplate": "warn",
        "noNegationElse": "warn"
      },
      "nursery": {
        "noFloatingPromises": "error",
        "noUselessElse": "warn"
      },
      "a11y": {
        "noAutofocus": "error",
        "noBlankTarget": {
          "level": "error",
          "options": {
            "allowDomains": []
          }
        }
      }
    }
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "single",
      "trailingCommas": "es5",
      "semicolons": "always"
    }
  },
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignore": [
      "node_modules",
      "dist",
      "build",
      ".next",
      "coverage"
    ],
    "include": [
      "src/**/*.ts",
      "src/**/*.tsx",
      "src/**/*.js",
      "src/**/*.jsx"
    ]
  }
}

CLAUDE.md Content (2)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"correctness": {
  "noUnusedVariables": "error",
  "noUnusedImports": "error",
  "noUndeclaredVariables": "error",
  "noConstAssign": "error",
  "noEmptyPattern": "error"
}

CLAUDE.md Content (3)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"suspicious": {
  "noDebugger": "error",
  "noConsoleLog": "warn",
  "noDoubleEquals": "error",
  "noExplicitAny": "error",
  "noShadowRestrictedNames": "error"
}

CLAUDE.md Content (4)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"style": {
  "noVar": "error",
  "useConst": "error",
  "useTemplate": "warn",
  "noNegationElse": "warn",
  "useShorthandArrayType": "warn"
}

CLAUDE.md Content (5)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"complexity": {
  "noStaticOnlyClass": "warn",
  "noUselessEmptyExport": "error",
  "noBannedTypes": "error"
}

CLAUDE.md Content (6)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"nursery": {
  "noFloatingPromises": "error",
  "noUselessElse": "warn"
}

CLAUDE.md Content (7)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "overrides": [
    {
      "include": ["*.test.ts", "*.test.tsx", "*.spec.ts"],
      "linter": {
        "rules": {
          "suspicious": {
            "noExplicitAny": "off"
          }
        }
      }
    },
    {
      "include": ["scripts/**"],
      "linter": {
        "rules": {
          "suspicious": {
            "noConsoleLog": "off"
          }
        }
      }
    },
    {
      "include": ["src/types/**/*.d.ts"],
      "linter": {
        "rules": {
          "style": {
            "useNamingConvention": "off"
          }
        }
      }
    }
  ]
}

CLAUDE.md Content (8)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  }
}

CLAUDE.md Content (9)

Additional code example for this claude.md.

biome-strict-linting-rules.sh

bash

# Lint files changed since main branch
biome check --changed

# Lint only staged files (for pre-commit hooks)
biome check --staged

CLAUDE.md Content (10)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        }
      },
      "style": {
        "useConst": {
          "level": "warn",
          "fix": "unsafe"
        },
        "useTemplate": {
          "level": "warn",
          "fix": "safe"
        }
      }
    }
  }
}

CLAUDE.md Content (11)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "useMyCustomEffect",
                "closureIndex": 0,
                "dependenciesIndex": 1
              }
            ]
          }
        },
        "useHookAtTopLevel": "error"
      },
      "a11y": {
        "noAutofocus": "error",
        "useKeyWithClickEvents": "error",
        "useButtonType": "error"
      }
    }
  }
}

CLAUDE.md Content (12)

Additional code example for this claude.md.

biome-strict-linting-rules.sh

bash

# Automatically migrate from ESLint/Prettier config
npx @biomejs/biome migrate eslint --write

# Or migrate Prettier config
npx @biomejs/biome migrate prettier --write

CLAUDE.md Content (13)

Additional code example for this claude.md.

biome-strict-linting-rules.yml

yaml

# GitHub Actions
name: Code Quality

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - run: npm ci
      - run: npx @biomejs/biome check --error-on-warnings

CLAUDE.md Content (14)

Additional code example for this claude.md.

biome-strict-linting-rules.sh

bash

# Pre-commit hook (using Husky)
npx husky add .husky/pre-commit "npx @biomejs/biome check --staged --no-errors-on-unmatched"

CLAUDE.md Content (15)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "files": {
    "ignore": [
      "node_modules",
      "dist",
      "build",
      ".next",
      "coverage",
      "**/*.min.js"
    ],
    "maxSize": 1000000
  }
}

CLAUDE.md Content (16)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  },
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[json]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

Features

Key capabilities and functionality

Comprehensive Biome linting configuration for production environments
Strict rule enforcement across correctness, suspicious, style, complexity, and nursery groups
File-specific overrides for tests, scripts, and type definitions
VCS integration with Git for efficient change-based linting
Custom severity levels and fix behavior configuration
React/JSX-specific rules for hooks and accessibility
Migration support from ESLint and Prettier configurations
CI/CD integration patterns for automated quality checks

Use Cases

Common scenarios and applications

Setting up production-ready Biome configuration for TypeScript projects
Migrating from ESLint and Prettier to unified Biome toolchain
Enforcing strict code quality standards in enterprise applications
Configuring file-specific linting rules for monorepo structures
Integrating Biome with Git workflows and pre-commit hooks
Optimizing linting performance for large codebases

Requirements

Prerequisites and dependencies

Create CLAUDE.md file in project root (./CLAUDE.md) or .claude/ directory (./.claude/CLAUDE.md)
Claude Code 1.0+ or Claude Desktop required for CLAUDE.md memory support and Biome configuration guidance
Write access to project root or .claude/ directory for rule file creation
Node.js 18+ or Bun runtime for running Biome CLI commands
Text editor with JSON support for editing biome.json configuration files
Biome package installed in project (npm install -D @biomejs/biome or pnpm add -D @biomejs/biome)
Git repository (recommended) for VCS integration and pre-commit hook setup
Understanding of JavaScript/TypeScript linting concepts to effectively configure Biome rules

Usage Examples

Practical code examples demonstrating common use cases and implementation patterns

Strict Production Biome Configuration

Complete Biome configuration with strict production rules, formatter settings, and VCS integration

strict-production-biome-configuration.json

json

{
  "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json",
  "formatter": {
    "enabled": true,
    "indentStyle": "tab",
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error",
        "noUnusedImports": "error"
      },
      "suspicious": {
        "noDebugger": "error",
        "noConsoleLog": "warn"
      }
    }
  },
  "vcs": {
    "enabled": true,
    "clientKind": "git"
  }
}

File-Specific Overrides for Tests

Configure Biome to allow relaxed rules for test files while maintaining strict standards for production code

file-specific-overrides-for-tests.json

json

{
  "linter": {
    "rules": {
      "recommended": true
    }
  },
  "overrides": [
    {
      "include": ["*.test.ts", "*.spec.ts"],
      "linter": {
        "rules": {
          "suspicious": {
            "noExplicitAny": "off"
          }
        }
      }
    }
  ]
}

Rule Severity and Fix Behavior Configuration

Customize rule severity levels and fix behavior for different rule types

rule-severity-and-fix-behavior-configuration.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        }
      },
      "style": {
        "useConst": {
          "level": "warn",
          "fix": "unsafe"
        },
        "useTemplate": {
          "level": "warn",
          "fix": "safe"
        }
      }
    }
  }
}

React/JSX Configuration with Hooks Rules

Biome configuration optimized for React projects with exhaustive dependencies and accessibility rules

react-jsx-configuration-with-hooks-rules.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "useMyCustomEffect",
                "closureIndex": 0,
                "dependenciesIndex": 1
              }
            ]
          }
        },
        "useHookAtTopLevel": "error"
      },
      "a11y": {
        "noAutofocus": "error",
        "useKeyWithClickEvents": "error"
      }
    }
  }
}

CI/CD Integration with GitHub Actions

GitHub Actions workflow to enforce Biome linting in CI/CD pipelines

ci-cd-integration-with-github-actions.yml

yaml

name: Code Quality

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - run: npm ci
      - run: npx @biomejs/biome check --error-on-warnings

Pre-commit Hook with Husky

Set up pre-commit hooks to run Biome checks on staged files before commits

pre-commit-hook-with-husky.sh

bash

# Install Husky
npm install --save-dev husky

# Initialize Husky
npx husky init

# Add pre-commit hook
npx husky add .husky/pre-commit "npx @biomejs/biome check --staged --no-errors-on-unmatched"

VS Code Editor Integration

VS Code settings for automatic formatting and linting with Biome on save

vs-code-editor-integration.json

json

{
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  },
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

Installation

Setup instructions and requirements

Configuration

Configuration settings and parameters

biome-strict-linting-rules.json

json

{
  "maxTokens": 8000,
  "temperature": 0.3,
  "systemPrompt": "You are a Biome linting expert focused on strict production-ready code quality configuration and validation",
  "compatibleWith": [
    "Claude Code",
    "Claude Desktop",
    "Claude Web"
  ]
}

Security Best Practices

Important security considerations

Biome configuration files (biome.json) may expose project structure, file patterns, or custom rule configurations - ensure biome.json is not committed to public repositories if it contains sensitive information
Pre-commit hooks running Biome checks can be bypassed with --no-verify flag - enforce Biome checks in CI/CD pipelines as a secondary validation layer
File-specific overrides may disable critical security-related linting rules - audit all overrides to ensure security rules remain enabled for production code
Biome migration from ESLint may introduce security vulnerabilities if ESLint security plugins are not properly migrated - manually verify security-related rules after migration
Nursery rules are experimental and may have bugs that could allow problematic code patterns - disable nursery rules in production or use with caution
VCS integration with --changed flag may skip linting on files that were modified outside tracked changes - use full project linting in CI/CD for comprehensive security checks
Biome rule configuration may expose internal code patterns or business logic if shared publicly - review biome.json before publishing open-source projects

Troubleshooting

Common issues and solutions

Biome reports errors on valid code after migration from ESLint
Use biome migrate command to convert ESLint rules. Review generated biome.json and adjust rule severity or add file-specific overrides using the overrides array for incompatible patterns.
Performance issues when linting large monorepo with thousands of files
Configure files.ignore to exclude node_modules, dist, build. Use --changed flag to lint modified files. Set files.maxSize to skip large files. Enable VCS integration for Git-aware linting.
Nursery rules causing false positives in production code
Nursery rules are experimental and may have bugs. Disable problematic rules by setting level to off in biome.json. Monitor Biome releases for stabilization and re-enable when moved to stable.
Editor not auto-fixing on save despite configuration
Verify Biome VS Code extension is installed. Check editor.codeActionsOnSave includes source.fixAll.biome set to explicit. Ensure biome.json formatter.enabled is true. Restart VS Code after.

CLAUDE.md Content

The main content for this claude.md.

biome-strict-linting-rules.json

json

{
  "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json",
  "formatter": {
    "enabled": true,
    "indentStyle": "tab",
    "indentWidth": 2,
    "lineWidth": 100,
    "lineEnding": "lf"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error",
        "noUnusedImports": "error",
        "noUndeclaredVariables": "error",
        "noConstAssign": "error"
      },
      "suspicious": {
        "noDebugger": "error",
        "noConsoleLog": "warn",
        "noDoubleEquals": "error",
        "noRedundantUseStrict": "warn"
      },
      "complexity": {
        "noStaticOnlyClass": "warn",
        "noUselessEmptyExport": "error"
      },
      "style": {
        "noVar": "error",
        "useConst": "error",
        "useTemplate": "warn",
        "noNegationElse": "warn"
      },
      "nursery": {
        "noFloatingPromises": "error",
        "noUselessElse": "warn"
      },
      "a11y": {
        "noAutofocus": "error",
        "noBlankTarget": {
          "level": "error",
          "options": {
            "allowDomains": []
          }
        }
      }
    }
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "single",
      "trailingCommas": "es5",
      "semicolons": "always"
    }
  },
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignore": [
      "node_modules",
      "dist",
      "build",
      ".next",
      "coverage"
    ],
    "include": [
      "src/**/*.ts",
      "src/**/*.tsx",
      "src/**/*.js",
      "src/**/*.jsx"
    ]
  }
}

CLAUDE.md Content (2)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"correctness": {
  "noUnusedVariables": "error",
  "noUnusedImports": "error",
  "noUndeclaredVariables": "error",
  "noConstAssign": "error",
  "noEmptyPattern": "error"
}

CLAUDE.md Content (3)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"suspicious": {
  "noDebugger": "error",
  "noConsoleLog": "warn",
  "noDoubleEquals": "error",
  "noExplicitAny": "error",
  "noShadowRestrictedNames": "error"
}

CLAUDE.md Content (4)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"style": {
  "noVar": "error",
  "useConst": "error",
  "useTemplate": "warn",
  "noNegationElse": "warn",
  "useShorthandArrayType": "warn"
}

CLAUDE.md Content (5)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"complexity": {
  "noStaticOnlyClass": "warn",
  "noUselessEmptyExport": "error",
  "noBannedTypes": "error"
}

CLAUDE.md Content (6)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

"nursery": {
  "noFloatingPromises": "error",
  "noUselessElse": "warn"
}

CLAUDE.md Content (7)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "overrides": [
    {
      "include": ["*.test.ts", "*.test.tsx", "*.spec.ts"],
      "linter": {
        "rules": {
          "suspicious": {
            "noExplicitAny": "off"
          }
        }
      }
    },
    {
      "include": ["scripts/**"],
      "linter": {
        "rules": {
          "suspicious": {
            "noConsoleLog": "off"
          }
        }
      }
    },
    {
      "include": ["src/types/**/*.d.ts"],
      "linter": {
        "rules": {
          "style": {
            "useNamingConvention": "off"
          }
        }
      }
    }
  ]
}

CLAUDE.md Content (8)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  }
}

CLAUDE.md Content (9)

Additional code example for this claude.md.

biome-strict-linting-rules.sh

bash

# Lint files changed since main branch
biome check --changed

# Lint only staged files (for pre-commit hooks)
biome check --staged

CLAUDE.md Content (10)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        }
      },
      "style": {
        "useConst": {
          "level": "warn",
          "fix": "unsafe"
        },
        "useTemplate": {
          "level": "warn",
          "fix": "safe"
        }
      }
    }
  }
}

CLAUDE.md Content (11)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "useMyCustomEffect",
                "closureIndex": 0,
                "dependenciesIndex": 1
              }
            ]
          }
        },
        "useHookAtTopLevel": "error"
      },
      "a11y": {
        "noAutofocus": "error",
        "useKeyWithClickEvents": "error",
        "useButtonType": "error"
      }
    }
  }
}

CLAUDE.md Content (12)

Additional code example for this claude.md.

biome-strict-linting-rules.sh

bash

# Automatically migrate from ESLint/Prettier config
npx @biomejs/biome migrate eslint --write

# Or migrate Prettier config
npx @biomejs/biome migrate prettier --write

CLAUDE.md Content (13)

Additional code example for this claude.md.

biome-strict-linting-rules.yml

yaml

# GitHub Actions
name: Code Quality

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - run: npm ci
      - run: npx @biomejs/biome check --error-on-warnings

CLAUDE.md Content (14)

Additional code example for this claude.md.

biome-strict-linting-rules.sh

bash

# Pre-commit hook (using Husky)
npx husky add .husky/pre-commit "npx @biomejs/biome check --staged --no-errors-on-unmatched"

CLAUDE.md Content (15)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "files": {
    "ignore": [
      "node_modules",
      "dist",
      "build",
      ".next",
      "coverage",
      "**/*.min.js"
    ],
    "maxSize": 1000000
  }
}

CLAUDE.md Content (16)

Additional code example for this claude.md.

biome-strict-linting-rules.json

json

{
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  },
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[json]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

Features

Key capabilities and functionality

Comprehensive Biome linting configuration for production environments
Strict rule enforcement across correctness, suspicious, style, complexity, and nursery groups
File-specific overrides for tests, scripts, and type definitions
VCS integration with Git for efficient change-based linting
Custom severity levels and fix behavior configuration
React/JSX-specific rules for hooks and accessibility
Migration support from ESLint and Prettier configurations
CI/CD integration patterns for automated quality checks

Use Cases

Common scenarios and applications

Setting up production-ready Biome configuration for TypeScript projects
Migrating from ESLint and Prettier to unified Biome toolchain
Enforcing strict code quality standards in enterprise applications
Configuring file-specific linting rules for monorepo structures
Integrating Biome with Git workflows and pre-commit hooks
Optimizing linting performance for large codebases

Requirements

Prerequisites and dependencies

Create CLAUDE.md file in project root (./CLAUDE.md) or .claude/ directory (./.claude/CLAUDE.md)
Claude Code 1.0+ or Claude Desktop required for CLAUDE.md memory support and Biome configuration guidance
Write access to project root or .claude/ directory for rule file creation
Node.js 18+ or Bun runtime for running Biome CLI commands
Text editor with JSON support for editing biome.json configuration files
Biome package installed in project (npm install -D @biomejs/biome or pnpm add -D @biomejs/biome)
Git repository (recommended) for VCS integration and pre-commit hook setup
Understanding of JavaScript/TypeScript linting concepts to effectively configure Biome rules

Usage Examples

Practical code examples demonstrating common use cases and implementation patterns

Strict Production Biome Configuration

Complete Biome configuration with strict production rules, formatter settings, and VCS integration

strict-production-biome-configuration.json

json

{
  "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json",
  "formatter": {
    "enabled": true,
    "indentStyle": "tab",
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error",
        "noUnusedImports": "error"
      },
      "suspicious": {
        "noDebugger": "error",
        "noConsoleLog": "warn"
      }
    }
  },
  "vcs": {
    "enabled": true,
    "clientKind": "git"
  }
}

File-Specific Overrides for Tests

Configure Biome to allow relaxed rules for test files while maintaining strict standards for production code

file-specific-overrides-for-tests.json

json

{
  "linter": {
    "rules": {
      "recommended": true
    }
  },
  "overrides": [
    {
      "include": ["*.test.ts", "*.spec.ts"],
      "linter": {
        "rules": {
          "suspicious": {
            "noExplicitAny": "off"
          }
        }
      }
    }
  ]
}

Rule Severity and Fix Behavior Configuration

Customize rule severity levels and fix behavior for different rule types

rule-severity-and-fix-behavior-configuration.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        }
      },
      "style": {
        "useConst": {
          "level": "warn",
          "fix": "unsafe"
        },
        "useTemplate": {
          "level": "warn",
          "fix": "safe"
        }
      }
    }
  }
}

React/JSX Configuration with Hooks Rules

Biome configuration optimized for React projects with exhaustive dependencies and accessibility rules

react-jsx-configuration-with-hooks-rules.json

json

{
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "useMyCustomEffect",
                "closureIndex": 0,
                "dependenciesIndex": 1
              }
            ]
          }
        },
        "useHookAtTopLevel": "error"
      },
      "a11y": {
        "noAutofocus": "error",
        "useKeyWithClickEvents": "error"
      }
    }
  }
}

CI/CD Integration with GitHub Actions

GitHub Actions workflow to enforce Biome linting in CI/CD pipelines

ci-cd-integration-with-github-actions.yml

yaml

name: Code Quality

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - run: npm ci
      - run: npx @biomejs/biome check --error-on-warnings

Pre-commit Hook with Husky

Set up pre-commit hooks to run Biome checks on staged files before commits

pre-commit-hook-with-husky.sh

bash

# Install Husky
npm install --save-dev husky

# Initialize Husky
npx husky init

# Add pre-commit hook
npx husky add .husky/pre-commit "npx @biomejs/biome check --staged --no-errors-on-unmatched"

VS Code Editor Integration

VS Code settings for automatic formatting and linting with Biome on save

vs-code-editor-integration.json

json

{
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  },
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

Installation

Setup instructions and requirements

Configuration

Configuration settings and parameters

biome-strict-linting-rules.json

json

{
  "maxTokens": 8000,
  "temperature": 0.3,
  "systemPrompt": "You are a Biome linting expert focused on strict production-ready code quality configuration and validation",
  "compatibleWith": [
    "Claude Code",
    "Claude Desktop",
    "Claude Web"
  ]
}

Security Best Practices

Important security considerations

Biome configuration files (biome.json) may expose project structure, file patterns, or custom rule configurations - ensure biome.json is not committed to public repositories if it contains sensitive information
Pre-commit hooks running Biome checks can be bypassed with --no-verify flag - enforce Biome checks in CI/CD pipelines as a secondary validation layer
File-specific overrides may disable critical security-related linting rules - audit all overrides to ensure security rules remain enabled for production code
Biome migration from ESLint may introduce security vulnerabilities if ESLint security plugins are not properly migrated - manually verify security-related rules after migration
Nursery rules are experimental and may have bugs that could allow problematic code patterns - disable nursery rules in production or use with caution
VCS integration with --changed flag may skip linting on files that were modified outside tracked changes - use full project linting in CI/CD for comprehensive security checks
Biome rule configuration may expose internal code patterns or business logic if shared publicly - review biome.json before publishing open-source projects

Troubleshooting

Common issues and solutions

Biome reports errors on valid code after migration from ESLint
Use biome migrate command to convert ESLint rules. Review generated biome.json and adjust rule severity or add file-specific overrides using the overrides array for incompatible patterns.
Performance issues when linting large monorepo with thousands of files
Configure files.ignore to exclude node_modules, dist, build. Use --changed flag to lint modified files. Set files.maxSize to skip large files. Enable VCS integration for Git-aware linting.
Nursery rules causing false positives in production code
Nursery rules are experimental and may have bugs. Disable problematic rules by setting level to off in biome.json. Monitor Biome releases for stabilization and re-enable when moved to stable.
Editor not auto-fixing on save despite configuration
Verify Biome VS Code extension is installed. Check editor.codeActionsOnSave includes source.fixAll.biome set to explicit. Ensure biome.json formatter.enabled is true. Restart VS Code after.

Resources

View on GitHub Documentation

CLAUDE.md Details

Temperature

0.3

Source

claudepro

Quick Actions

Related CLAUDE.mds

Production Codebase Auditor

Expert in comprehensive production codebase analysis with Zod validation enforcement, security vulnerability detection, and code consolidation strategies

React Next Js Expert

Transform Claude into a React and Next.js specialist with deep knowledge of modern patterns, performance optimization, and best practices

React Expert

Transform Claude into a React and Next.js specialist with deep knowledge of modern patterns, performance optimization, and best practices

Hire Claude Developers

Growing community of AI engineers actively building with Claude

Active community1,700/month

Growth rateMonth 2

Specialized AI talent pool

30-day featured visibility

Early-stage pricing advantage

View Pricing & Post Job

Live in 5 minutes • Growing community

Resources

View on GitHub Documentation

CLAUDE.md Details

Temperature

0.3

Source

claudepro

Quick Actions

Hire Claude Developers

Growing community of AI engineers actively building with Claude

Active community1,700/month

Growth rateMonth 2

Specialized AI talent pool

30-day featured visibility

Early-stage pricing advantage

View Pricing & Post Job

Live in 5 minutes • Growing community

Strict Production Biome Configuration

File-Specific Overrides for Tests

Rule Severity and Fix Behavior Configuration

React/JSX Configuration with Hooks Rules

CI/CD Integration with GitHub Actions

Pre-commit Hook with Husky

VS Code Editor Integration

Reviews (0)

Biome Strict Linting Rules

Strict Production Biome Configuration

File-Specific Overrides for Tests

Rule Severity and Fix Behavior Configuration

React/JSX Configuration with Hooks Rules

CI/CD Integration with GitHub Actions

Pre-commit Hook with Husky

VS Code Editor Integration

Reviews (0)

Category

Temperature

Source

Production Codebase Auditor

React Next Js Expert

React Expert

Hire Claude Developers