biomejs/biome - CodSpeed

biome

Blog Docs Changelog

Performance History

Latest Results

refactor(css_parser): select SCSS recovery kinds at call sites

dbezrukov/scss-n3-query-unary-values

40 minutes ago

fix(console): treat a closed pipe as end of output `biome check | head`, quitting a pager early, or a terminal that goes away while Biome is still printing all leave Biome writing into a closed pipe. Rust ignores SIGPIPE, so the write fails with `ErrorKind::BrokenPipe` instead of killing the process, and `EnvConsole` unwrapped that error. The resulting panic was then made worse by the panic handler itself, which used `eprintln!` on the same already-failed stderr: a second panic inside the handler makes Rust abort, so the report the user was meant to see was replaced by SIGABRT and a core dump. Two changes, both narrow: - `EnvConsole` routes its writes through `ignore_broken_pipe`, which drops a `BrokenPipe` error and keeps panicking on anything else. A reader that goes away is an ordinary way to say "that is enough"; any other write error is still a bug. - The panic handler writes to stderr with `writeln!` and ignores the result, instead of `eprintln!` which panics when the write fails. A failure to print the report must not escalate into an abort. Covers #11817, where the abort is reported with the recovered panic message `called Result::unwrap() on an Err value: Os { code: 32, kind: BrokenPipe }`.

Mario-Mohar:fix/console-broken-pipe-abort

9 hours ago

fix(biome_js_analyze/noVueSideEffectsInComputed): resolve Vue, catch direct writes Two problems found in review. `Vue.set()` was matched on the name alone, so a local object owning a `set` method was reported as a reactive write. Resolve the receiver through the semantic model instead, with `is_vue_api_reference`, which accepts only the `Vue` global or a binding imported from `vue` -- and, as a side effect of going through that helper, Vue 2's named `set` export as well. A bare identifier in a write position is a `JsIdentifierAssignment`, and the parser drops the inner `JsReferenceIdentifier`, so `count = 1` and `count++` on a setup binding reached neither the scope filter nor mutation detection. Walk `AnyJsIdentifierReference` instead and report an assignment target directly. The upstream ESLint rule misses these because its selector only matches an identifier that is the object of a member expression; the scope filters are unchanged, so a binding declared inside the getter is still the getter's own. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

changbaebang:feat/no-vue-side-effects-in-computed

13 hours ago

fix(type_inference): stop recursive unknown indexed access growth

dyc3/fix-generic-member-substitution

20 hours ago

fix(type_inference): stop recursive unknown indexed access growth

dyc3/fix-generic-member-substitution

21 hours ago

feat(type_inference): support mapped keyof types

dyc3/support-mapped-keyof-types

22 hours ago

test(module_graph): add complex type inference benchmarks (#11845)

main

22 hours ago

test(module_graph): add complex type inference benchmarks

dyc3/type-inference-integration-benchmarks

22 hours ago

Latest Branches

-7%

fix(scss): support unary expressions in query values#11974

8 days ago

8841951

dbezrukov/scss-n3-query-unary-values

0%

fix(console): treat a closed pipe as end of output#11971

11 hours ago

211c4a0

Mario-Mohar:fix/console-broken-pipe-abort

+8%

feat(biome_js_analyze): implement noVueSideEffectsInComputed#11968

15 hours ago

ad90359

changbaebang:feat/no-vue-side-effects-in-computed

© 2026 CodSpeed Technology

Home Terms Privacy Docs