biomejs/biome - CodSpeed

biome

Blog Docs Changelog

Performance History

Latest Results

[autofix.ci] apply automated fixes

dyc3/html-style-attribute-css

11 hours ago

fix(format/html): preserve the content of preformatted elements `<textarea>`, `<xmp>` and `<plaintext>` were formatted like ordinary markup, so their text had its newlines and runs of spaces collapsed. That is a rendering change rather than a cosmetic one: all three are rendered with a `white-space` value that keeps the whitespace, and for `<textarea>` the text is the value of the form field. The lexer now reads them as raw text, the way it already did for `<pre>`, which keeps the leading and trailing whitespace in the token instead of losing it to trivia. On the formatter side the hardcoded verbatim tag list is replaced by a lookup through `get_css_whitespace`, which already encoded the correct set but was dead code. `listing` renders the same way but has no tag keyword, so it only gets the formatter half of the fix. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

dyc3/html-whitespace-sensitive-content

11 hours ago

feat(format/html): format the style attribute as CSS The value of a `style` attribute is a list of CSS declarations, but it was printed exactly as written, so whatever spacing it was pasted with stayed. It now goes through the CSS formatter, the way a `<style>` element already did. An attribute is not a block: the declarations stay on the tag's line while they fit and break onto their own lines once they do not, and the last one only takes a semicolon in the broken form. That is what `CssEmbeddingKind::HtmlStyleAttribute` selects, reusing the snippet root that already parses a bare declaration list. Such a list ends at the end of its input rather than at a `}`, so the final semicolon is now optional there — `style="color: red"` is how everyone writes it. Two supporting fixes: The trailing hard line break after embedded content moves from the `EndEmbedded` tag into the callers that wrap it. A block wants that break; an attribute value must not have one, since it would force the attribute onto its own line whatever its length. The formatter now knows which ranges have a parsed document waiting, as the JavaScript formatter already did. A hole nothing fills prints as nothing, so leaving one for a value that was never parsed would silently empty the attribute. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

dyc3/html-style-attribute-css

11 hours ago

feat(useSortedClasses): sort sort_v4 candidates by property signature A candidate's primary Tailwind sort key is the full set of properties its declarations touch, not a single representative property: compiled candidates order by the first differing property-order index after the shared prefix of their ascending index lists, a list that exhausts first sorts after the longer one, and declaration count breaks the tie. Single-property approximation misplaced every utility whose leading declaration differs from its sort position: size-* (height+width) after h-*, container (keyed by --tw-container-component) after display, font-weight utilities behind transition, arbitrary ring values behind shadow. Take the (order, count) pairs verbatim from compileAstNodes' propertySort instead of re-parsing compiled CSS text, deduplicate them into a generated SIGNATURE_POOL, and compare pool slices in the sort key. Fixture expectations are cross-checked against prettier-plugin-tailwindcss 0.8.0; the size-* divergence documented previously is now plugin-exact, and group/peer parity is pinned.

johncarmack1984:feat/use-sorted-classes-property-signature

15 hours ago

feat(useSortedClasses): sort sort_v4 candidates by property signature A candidate's primary Tailwind sort key is the full set of properties its declarations touch, not a single representative property: compiled candidates order by the first differing property-order index after the shared prefix of their ascending index lists, a list that exhausts first sorts after the longer one, and declaration count breaks the tie. Single-property approximation misplaced every utility whose leading declaration differs from its sort position: size-* (height+width) after h-*, container (keyed by --tw-container-component) after display, font-weight utilities behind transition, arbitrary ring values behind shadow. Take the (order, count) pairs verbatim from compileAstNodes' propertySort instead of re-parsing compiled CSS text, deduplicate them into a generated SIGNATURE_POOL, and compare pool slices in the sort key. Fixture expectations are cross-checked against prettier-plugin-tailwindcss 0.8.0; the size-* divergence documented previously is now plugin-exact, and group/peer parity is pinned.

johncarmack1984:feat/use-sorted-classes-property-signature

16 hours ago

feat(useSortedClasses): order by name and resolve dashed statics in sort_v4 (#11041)

main

18 hours ago

fix(parse/html): accept mixed case doctype declarations (#11071)

main

19 hours ago

test(format/html): enable prettier's vue snapshot tests (#11070)

main

20 hours ago

Latest Branches

+5%

feat(format/html): format the style attribute as CSS#11080

11 hours ago

97ae9ff

dyc3/html-style-attribute-css

0%

fix(format/html): preserve the content of preformatted elements#11077

17 hours ago

462fcf0

dyc3/html-whitespace-sensitive-content

0%

feat(useSortedClasses): sort sort_v4 candidates by property signature#11076

3 days ago

e2235ed

johncarmack1984:feat/use-sorted-classes-property-signature

© 2026 CodSpeed Technology

Home Terms Privacy Docs