ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
ESLint 9 introduces array-based configuration, changing how eslint-config-prettier is composed, while Prettier continues to enforce indentation, quotes, semicolons, and other stylistic rules that also appear in ESLint's core style checks. The overlap creates ambiguity about whether formatting should be handled by linting or a dedicated formatter, affecting e
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
Integration gap between build pipeline and framework linters Meteor's isobuild pipeline compiles and bundles application code but does not include accessibility auditing as a built-in step. Frontend frameworks integrated with Meteor — Blaze, React, Vue, and Svelte — each provide their own linting ecosystems (eslint-plugin-jsx-a11y for React, vue-eslint-plugi
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
The goal is to set a CI gate that blocks new warning‑level issues while preventing unnecessary merge rejections from existing warnings. Using `--max-warnings=0` forces a non‑zero exit code on any warning, which is strict but requires a clean baseline before enabling; `--quiet` hides all warnings and keeps the exit code zero, allowing merges but masking emerg
eslint
javascript
biome