a-c-mBiome Suppressed
A fast, lightweight drop-in wrapper for biome check (https://biomejs.dev/) that maintains an error baseline and only fails on new errors. Automatically improves the baseline when fewer errors are found.
Available as both biome-suppressed and bs commands for convenience.
Built because https://eslint.org/docs/latest/use/suppressions looked awesome. 🚀
(Written mostly by Claude Code - so use at your own risk)
Installation
# Install as dev dependency (recommended)
npm install --save-dev biome-suppressed
# Or install globally
npm install -g biome-suppressedFrom Source (Optional)
# Clone and link
git clone https://github.com/a-c-m/biome-suppressed.git
cd biome-suppressed
npm linkKey Features
- Drop-in wrapper: Use
bs checkinstead ofbiome check - True drop-in replacement: Check-only by default (use
--writeto apply fixes) - Auto-improvement: Updates baseline automatically when errors decrease
- Performance: <50ms overhead on top of biome execution
- Fail on regression: Exit 1 only when new errors are introduced
- CI-friendly:
--suppression-fail-on-improvementfor strict CI environments - Token efficient: Minimal output for error resolution
Usage
Initial Setup
# Initialize with current error state (run once)
bs init
# Output: ✅ Baseline created with 18649 errorsNormal Development
# Check for new errors (default behavior, like biome check)
bs check
# Output: ✅ No new errors (18649 existing errors suppressed)
# Check and apply fixes (like biome check --write)
bs check --write
# Output: ✅ No new errors (18649 existing errors suppressed)After Fixing Errors
bs check
# Output: 🎉 Improvement detected! 18649 → 18500 errors (-149)
# 📊 Baseline updated automaticallyWhen New Errors Are Introduced
bs check
# Output: ❌ Found 3 new errors:
#
# lint/style/useNamingConvention (2 errors):
# src/components/Button.tsx:42
# src/utils/helpers.ts:15
#
# lint/suspicious/noExplicitAny (1 error):
# src/types/api.ts:8
#
# Fix strategies:
# • Run: npx biome check --write src/components/Button.tsx src/utils/helpers.ts src/types/api.ts
# • Or accept: bs update
# Exit code: 1Commands
check [options] [files...]- Check for new errors (default: .)init [files...]- Create initial baseline (default: .)update [files...]- Update baseline with current errors (default: .)clear- Remove baseline filestatus- Show baseline informationchart [output-file]- Generate interactive HTML chart from git history (requires git and jq)
Options for check:
--write- Apply fixes (like biome check --write)--skip-suppression-update- Don't update baseline on improvement--suppression-fail-on-improvement- Fail if fewer errors than baseline (CI mode)
Note on update Command
The update command is intentionally de-emphasized in error messages to discourage lazy fixes. While it's available for legitimate use cases (bulk refactoring, dependency upgrades, etc.), the tool's error output promotes fixing errors properly with --write instead of just accepting them into the baseline. This is by design to prevent AI assistants and developers from taking the easy path of suppressing errors rather than fixing them.
Integration
Package.json Scripts
{
"scripts": {
"lint": "bs check",
"lint:fix": "bs check --write",
"lint:ci": "bs check --suppression-fail-on-improvement",
"lint:init": "bs init",
"lint:update": "bs update",
"lint:status": "bs status",
"lint:clear": "bs clear",
"lint:chart": "bs chart",
"lint:strict": "biome check --write ."
}
}CI/CD Integration
# .github/workflows/lint.yml
- name: Lint check
run: npm run lint:ci
# Fails on new errors OR unexpected improvements (strict mode)
# Alternative: Auto-updating mode
- name: Lint check (auto-update)
run: npm run lint
# Fails only on new errors, auto-updates on improvementsBenefits
- Legacy Codebase Friendly: Adopt Biome without fixing thousands of existing errors first
- Always Improving: Automatic baseline updates reward code quality improvements
- Fast & Lightweight: <50ms overhead, single file implementation
- CI/CD Ready: Proper exit codes, clear error reporting
- Zero Config: Works with existing biome.jsonc configuration
- Drop-in Replacement: Minimal changes to existing workflows
How It Works
- Runs
biome check --write --reporter=githubto fix what can be fixed - Parses GitHub Actions format output for structured error data
- Compares current errors against stored baseline using MD5 fingerprints
- Updates baseline automatically when errors decrease
- Fails only when new errors are introduced (not in baseline)
- Provides actionable next steps for error resolution
File Structure
.
├── index.js # Zero dependencies, under 500 lines
├── package.json # CLI metadata with bin commands
└── README.md # This documentationVisualization
Track your progress with the chart command! Generate an interactive HTML dashboard showing:
- Historical trend charts for last 4 weeks and all time
- Leaderboards showing who's fixing vs adding suppressions
- Summary statistics including peak count and total reduction percentage
# Generate chart (requires git and jq)
bs chart
# Or specify custom output file
bs chart docs/suppression-progress.htmlThe generated HTML file is self-contained and can be shared with your team or archived for historical tracking.
Architecture
- Single file: Zero dependencies except biome itself
- GitHub reporter: Token-efficient error parsing vs JSON format
- MD5 fingerprinting: Fast error identification and comparison
- Auto-improvement: Ratcheting system that always moves toward better code quality
- Error grouping: Token-efficient display grouped by rule type
- Progress tracking: Git-based chart generation for visualizing improvements
This tool enables adopting Biome on legacy codebases while maintaining development velocity and encouraging continuous improvement.