biome-js

What problem does it solve?

BiomeJS configuration can be complex, requiring careful setup of extends, file patterns, and project-specific overrides. This skill provides practical guidance to configure BiomeJS across projects, ensuring consistent linting and formatting configurations.

Core Features & Use Cases

• Shows how to extend shared configs via npm exports while maintaining explicit files.includes.
• Demonstrates monorepo inheritance and how to apply per-package overrides.
• Provides concrete patterns for UI projects, root configs, and typical exclusions.

Quick Start

Create or update biome.jsonc at the root of your project with an extends entry (for example, ["@sablier/devkit/biome"]) and a files.includes pattern appropriate for your project (e.g., "/*.{js,json,jsonc,ts}", "!node_modules//*"). If working in a monorepo, ensure the root biome.jsonc is inherited by packages via the ["//"] syntax and add package-specific overrides as needed.