ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #biome
Biome focuses on high-performance linting and formatting for JavaScript and TypeScript but lacks a native engine for date-time manipulation. While the linter can enforce syntax patterns, it does not provide a mechanism to perform logic-based validation for regional timezone conversions or specific offset calculations. The goal is to ensure that all date-time
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
Background Biome's LSP implementation currently relies on the standard $/cancelRequest notification from the client to abort in‑flight formatting or linting. The server does not expose a configurable per‑request timeout, and the formatter processes a file in a single pass without yielding, so cancellation only takes effect after the current file's parse comp
Formatter output divergence during incremental adoption Biome's built-in migration command converts ESLint and Prettier configurations, but the formatter produces different output than Prettier for certain syntax patterns. When migrating a small application without downtime, both toolchains must coexist during the transition window. Constraint: simultaneous
Biome provides a unified toolchain for CSS formatting and linting, utilizing a deterministic AST-based approach to replace standalone tools like Prettier. While this architecture ensures consistent output regardless of input spacing, the transition involves moving from a separate configuration ecosystem to a centralized biome.json file. When migrating comple
Configuration file not found – biome.json configuration resolution Goal: Clarify whether a .biomeignore file at the repository root takes precedence over the files.ignore array defined in a biome.json configuration when both are present, particularly in setups with nested biome.json files in a monorepo. Constraints: Biome’s configuration lookup walks upward
When utilizing a monorepo structure with nested biome.json files, the ignore property occasionally fails to resolve paths consistently across different environments. While local development respects the root-level ignores, production CI/CD pipelines often process files that should be excluded based on nested glob patterns. The discrepancy arises when complex
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
When adopting Biome incrementally, teams must decide whether a particular style concern should be managed by the formatter or the linter. The formatter is intended to own layout‑related rules, while the linter focuses on correctness, but some linter rules can still overlap with formatter output, creating potential conflicts during migration. The goal is to e
javascript