ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
If Biome ignores your custom rules, the problem often lies in the config file location, cache, rule names, or TypeScript settings. Follow this diagnostic guide to identify and fix the issue quickly.
Discover how Biome’s zero‑config mode lets you lint and format JavaScript/TypeScript without a .biomerc file, the trade‑offs of opinionated defaults, and how to audit or override rules for team‑specific standards.
Use ESLint’s <code>overrides</code> to let <code>console.log</code> in test files while keeping <code>no-console</code> for production code. A practical config, run‑time verification, and common pitfalls are covered.
Goal Establish a consistent policy for running Biome's in-place fix pass (`biome check --write`) in CI and pre-commit hooks, deciding whether to include unsafe fixes that may change runtime behavior. Constraints and uncertainty Biome edits files directly and provides no backup or snapshot mechanism; version control is the only rollback. The flag surface for
Biome's linter and formatter cover syntax and style, but the toolchain ships no native date-time utility. Projects that handle regional time zones therefore depend on the JavaScript Date object and the Intl API, whose behavior is sensitive to the host environment's locale and time zone settings. The documented rule set flags deprecated Date methods, but time
Background Biome 1.0.0 introduced the --watch flag to automatically re‑run linting when source files change. On Windows the default watcher is chokidar , which has documented limitations on network drives and certain file systems, causing the flag to silently fail. The Biome team has acknowledged the issue but has not yet released an official Windows‑compati
Biome utilizes a strict schema for its biome.json file to manage linting rules and formatting configurations. When upgrading between major versions, the configuration structure often undergoes breaking changes to accommodate new toolchain capabilities. Currently, there is no native, automated rollback mechanism to programmatically revert the configuration to
biome
eslint
javascript