Using ESLint Overrides to Tighten Rules on New Code Only
Learn how ESLint overrides let you enforce stricter rules on new or modified files while keeping legacy code tolerant, with a concrete config example and verification steps.
Loading…
ReadMeFeed / Community knowledge
#linting
Real questions. Useful conversations. Find the people who know your stack.
eslintDiagnosing Persistent Import Order Failures in Biome
A step-by-step diagnostic guide for Biome import order failures that persist across config changes, covering config precedence, cache staleness, regex syntax, version mismatches, and IDE/CLI alignment.
Fine‑Tune Linting in a Monorepo with ESLint Overrides
In a large monorepo, a single ESLint config can’t satisfy every package. ESLint’s "overrides" let you tailor rules per package or language, keeping a single config file while avoiding false positives. This guide shows how, with a concrete example, the trade‑offs, and best‑practice actions.
Troubleshooting Biome Linting: When Custom Rules Don’t Apply
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.
biomeBiome’s Zero‑Config Linting: Faster Onboarding, Simpler CI, and What to Watch For
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.
Fine‑Grained ESLint Linting: Using Overrides to Allow console.log in Tests Only
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.
Biome fix pass scope—safe versus unsafe edits in automation
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 vs Prettier: Should Style Corrections Reside in the Linting Pipeline?
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 lint rule gap for regional time zone conversion logic
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
javascript