biome-js

Quick guidance for BiomeJS configuration based on Sablier project patterns. Extend shared configs via npm package exports. The consuming project must always provide its own files.includes : For UI projects, extend both base and ui configs: In monorepos, workspace configs inherit from root using "//" : Always specify files.includes explicitly. Common patterns: Exclusions: !node_modules/**/* , !**/generated , !dist Relax strict rules in test files: Disable sorting and compact formatting for generated code: Enforce barrel imports for specific modules: Standard pattern for pre-commit hooks: The separate noUnusedImports pass enforces import cleanup only at commit time, not during development. For frontend projects with Tailwind CSS: Biome v2.4.0+ auto-enables CSS Modules parsing for *.module.css , so explicit "cssModules": true is usually unnecessary unless your project needs non-standard behavior. "No files matched" : Check files.includes patterns match your file structure. Conflicting rules : Overrides are applied in order; later overrides take precedence. Schema errors : Use local schema reference for IDE support: Biome handles JS/TS/JSON/CSS formatting.