@sebastienrousseau/biome-config

What is @sebastienrousseau/biome-config?

@sebastienrousseau/biome-config is an enterprise-grade, shareable configuration for Biome—the ultra-fast toolchain for web projects written in Rust. Designed to replace complex ESLint and Prettier setups with a single, blazingly fast binary, this package provides vetted, deterministic linting and formatting defaults for JavaScript, TypeScript, JSX, TSX, and JSON.

By consolidating formatting and linting into a unified engine, development teams achieve sub-millisecond feedback loops during local editing and CI/CD pipelines. This package adheres strictly to the OpenSSF Best Practices badge program and achieves top-tier security ratings via Scorecard audits.

Explore the complete Installation Guide, review the comprehensive Usage Documentation, inspect the API Reference, or discover AI integrations via the Model Context Protocol (MCP).

Why Developers Choose @sebastienrousseau/biome-config

Modern JavaScript and TypeScript repositories frequently suffer from configuration fatigue, conflicting rules between linters and formatters, and slow execution times. @sebastienrousseau/biome-config solves these challenges:

• Unmatched Speed: Powered by Biome's Rust architecture, linting and formatting execute up to 35x faster than ESLint and Prettier combined.
• Zero Runtime Dependencies: The package adds exactly zero runtime dependencies to your project, guaranteeing zero supply-chain risk and lightning-fast package manager installs.
• Dual Module Compatibility: Ready for both ECMAScript Modules (import) and CommonJS (require), accommodating legacy codebases and modern ESM architectures alike.
• TypeScript Type Safety: Bundled TypeScript definitions ensure all configuration objects and helper functions validate under strict tsc checks.
• Enterprise Security & Supply Chain Defense: Every release is signed and verified with automated OpenSSF Scorecard auditing, SLSA Provenance generation, and continuous CodeQL security scanning.

How to Get Started in 3 Steps

Integrating @sebastienrousseau/biome-config into any new or existing repository requires only three simple steps.

Step 1: Install the Package

Install the configuration along with Biome as development dependencies:

# Using npm
npm install --save-dev @sebastienrousseau/biome-config @biomejs/biome

# Using pnpm
pnpm add -D @sebastienrousseau/biome-config @biomejs/biome

# Using yarn
yarn add -D @sebastienrousseau/biome-config @biomejs/biome

For advanced package manager configurations and offline workflows, consult our Installation Guide.

Step 2: Configure biome.json

Create or update your biome.json file at the root of your project to extend the shared configuration:

{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["@sebastienrousseau/biome-config"]
}

Learn how to customize specific lint rules, indentation, line widths, and ignore patterns in the Usage Guide.

Step 3: Run Biome via npm Scripts

Add the standard quality scripts to your package.json:

{
  "scripts": {
    "lint": "biome check .",
    "lint:fix": "biome check --write .",
    "format": "biome format --write ."
  }
}

Now you can execute npm run lint or npm run lint:fix to automatically format and fix your entire codebase in milliseconds.

Key Features & Architecture

For a detailed breakdown of all exported configuration files and schema fields, visit the Reference Guide.

Frequently Asked Questions (FAQ)

What makes Biome different from ESLint and Prettier?

Biome is written in Rust and integrates formatting, linting, and syntax analysis into a single unified binary. Instead of running separate processes for formatting (Prettier) and linting (ESLint) with conflicting plugin ecosystems, Biome handles both in a fraction of the time with unified AST parsing.

Can I override individual rules in my project?

Yes. Biome's extends mechanism allows you to override any specific formatter, linter, or syntax rule directly in your local biome.json. See the Usage Guide for concrete examples.

Is @sebastienrousseau/biome-config safe for production CI/CD?

Yes. The package complies with the OpenSSF Best Practices criteria, carries an active OpenSSF Scorecard audit, and contains zero runtime dependencies. Every release undergoes continuous automated regression testing and CodeQL analysis.

How does this package support AI and agentic workflows?

The project includes a Model Context Protocol (MCP) configuration, enabling LLM coding assistants and AI agents to understand, validate, and execute repository configuration tasks autonomously.