Comparing changes

Visitable used to automatically derive NodeWithMetadata. This was problematic for two reasons: 1. Visitable just implemented the default simple case, which require a tag to skip this derive for more complex setups. 2. Visitable is feature flagged behind the `visitable` flag, but it was easy to forget this flag when manually deriving NodeWithMetadata, which would cause build failures. We run `test --all-features` in CI but don't build each crate individually, which means CI can pass (due to interdependent code) but publish can fail (due to independent builds). We dry-run but that can fail for breaking changes, making it a bit of a "boy-who-cried-wolf" as it can have either legitimate build failures, or just be a sign we need to cut a release due to breaking changes. Right now releases are failing due to the Visitable/NodeWithMetadata issue, so this change does a few things: 1. Implement derive NodeWithMetadata, so that all nodes can derive instead of relying on the magic in derive(Visitable). 2. Delete said magic from derive(Visitable). 3. Add a test in CI which iterates over each crate and builds it. This is all a very large change but was largely scripted (fancy find and replace) to just add derive calls everywhere. There were a few places which needed more advanced derives, to add new metadata, but largely most nodes now do what they did before but without magical derive(), and the build works!

#825) The current system of `#[in_range]` is a little clunky, and has problems with extensibility - as adding new variants would require new attributes and touching proc macros, which is contributor unfriendly. This change introduces a set of generics that replace these, instead. This is a much simpler way to handle this and more closely follows the rest of the codebase conventions: derives Parse/Peek etc.

…eplacement is shorter. (#827) Currently if ReduceTimeUnits encounters a length like `0050ms`, it will translate it to `.05s` despite `50ms` and `.05s` being equivalent lengths. This is due to it counting the length of the uncompacted cursor. This change introduces a new `may_compact()` method in SourceCursor which uses quick heuristics to determine if a cursor could be compacted. This let's us check if we should then calculate the compacted length of the cursor to see if compaction is sufficient to minify the unit. The result is that "bloated" dimensions like `0050ms` won't switch units unnecessarily, and will instead allow the CompactCursorWriteSink to do its thing and translate it to `50ms`.

Currently the minifier will always preserve the `+` sign, even when it's redundant. For example `+5s` will be "minified" as `+5s` despite it being possible to remove the `+` and compact to `5s`. This is largely because the `+` sign is _sometimes_ required, for example in AN+B syntax where `5n+1` _must_ be serialised as `5n+1`; `5n1` is invalid. Luckily, we have a single reserved bit in the Number bitflags. We can leverage this to store a "preserve sign" flag, which we can set during parse of AN+B syntax. Then during compaction we can check the "preserve sign" flag to check if we can safely elide the `+` or render it.

In #828 we introduced sign preservation to ensure An+B syntax was preserved while still eliding redundant signs during minification. However we were a little too conservative. An+B integer expressions like `nth-child(+5)` can be equally represented by `nth-child(5)`. This change removes the preserve_sign() call on integer expressions, allowing these to be properly minified.

Updates to the latest specs from w3c/csswg-drafts ## Changes from w3c/csswg-drafts Updated from [`f5642b9`](w3c/csswg-drafts@f5642b9) to [`7e27ad7`](w3c/csswg-drafts@7e27ad7) (18 commits) - [034f50a](w3c/csswg-drafts@034f50a) [fill-stroke-3][filter-effects-1][filter-effects-2][[matrix][motion-1] Changed group from fxtf to csswg - [35025cc](w3c/csswg-drafts@35025cc) [css-anchor-position-1] Add wip example - [41a4d08](w3c/csswg-drafts@41a4d08) [css-animations-1] Make `@keyframes` name disallow empty `<string>` (#13151) - [6270271](w3c/csswg-drafts@6270271) [mediaqueries-4][mediaqueries-5][editorial] Fixed typo - [e21fc71](w3c/csswg-drafts@e21fc71) [mediaqueries-5][editorial] Updated Changes section - [d787c8c](w3c/csswg-drafts@d787c8c) [css-color-4][editorial] corrected attribution for EdgeSeeker - [7bb2269](w3c/csswg-drafts@7bb2269) [css-color-4][editorial] Small clarity improvements - [40a7d63](w3c/csswg-drafts@40a7d63) [css-color-4][editorial] Clarified the original algorithm to be just one option, give a more specific name - [381dd9d](w3c/csswg-drafts@381dd9d) [css-color-4] dded pseudocode for the ray trace gamut mapping algorithm, #10579 - [d08e1be](w3c/csswg-drafts@d08e1be) [css-color-4][editorial] Clear up formatting of footnotes - [8228ada](w3c/csswg-drafts@8228ada) [css-color-4][editorial] algorithm formatting - [b5020a7](w3c/csswg-drafts@b5020a7) [mediaqueries-5][editorial] Unified media feature references - [bc67c7f](w3c/csswg-drafts@bc67c7f) [mediaqueries-5][editorial] Added changes since level 4 - [ccc16f1](w3c/csswg-drafts@ccc16f1) [css-color-4][editorial] fix typos noted in review comments #10579 - [7d4ae56](w3c/csswg-drafts@7d4ae56) [css-color-4] Correct ray trace algorithm to not overwrite `end`, #10579 - [b31fd0a](w3c/csswg-drafts@b31fd0a) [css-color-4][editorial] formatting for array elements in algorithms - [505ed8f](w3c/csswg-drafts@505ed8f) typo - [7e27ad7](w3c/csswg-drafts@7e27ad7) [css-multicol-1][editorial] Updated WPTs [View full diff](w3c/csswg-drafts@f5642b9...7e27ad7)

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [lightningcss-cli](https://redirect.github.com/parcel-bundler/lightningcss) | [`1.30.2` → `1.31.1`](https://renovatebot.com/diffs/npm/lightningcss-cli/1.30.2/1.31.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/lightningcss-cli/1.31.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/lightningcss-cli/1.30.2/1.31.1?slim=true) | --- ### Release Notes <details> <summary>parcel-bundler/lightningcss (lightningcss-cli)</summary> ### [`v1.31.1`](https://redirect.github.com/parcel-bundler/lightningcss/compare/v1.31.0...6993d9f1d3cd69030c5976cd8860361b7679f68d) [Compare Source](https://redirect.github.com/parcel-bundler/lightningcss/compare/v1.31.0...6993d9f1d3cd69030c5976cd8860361b7679f68d) ### [`v1.31.0`](https://redirect.github.com/parcel-bundler/lightningcss/releases/tag/v1.31.0) [Compare Source](https://redirect.github.com/parcel-bundler/lightningcss/compare/v1.30.2...v1.31.0) #### Features - [Implement scroll-state container queries](https://redirect.github.com/parcel-bundler/lightningcss/commit/220b39039d83d1d5e9c488c21242bede49834a97) - [Allow @property to be nested inside at-rules](https://redirect.github.com/parcel-bundler/lightningcss/pull/1090) - [Support print-color-adjust property](https://redirect.github.com/parcel-bundler/lightningcss/pull/1102) - [Support `<string>` in @property syntax](https://redirect.github.com/parcel-bundler/lightningcss/pull/1134) - [Add :state() pseudo-class support](https://redirect.github.com/parcel-bundler/lightningcss/pull/1133) - [Reduce min(), max() and clamp() with number arguments](https://redirect.github.com/parcel-bundler/lightningcss/pull/1131) - [Support name-only @container queries](https://redirect.github.com/parcel-bundler/lightningcss/pull/1125) - #### Fixes - [Ensure compiled range media queries are correctly parenthesised](https://redirect.github.com/parcel-bundler/lightningcss/pull/1114) - [Add quotes to font-families with multiple consecutive spaces](https://redirect.github.com/parcel-bundler/lightningcss/pull/1064) - [Do not remove whitespace in token lists](https://redirect.github.com/parcel-bundler/lightningcss/commit/32f1f52f025fc43887b20448cc9646b09ef96329) - [Fix whitespace handling in view transition pseudos](https://redirect.github.com/parcel-bundler/lightningcss/commit/8986055badf22d508a197dc8ef368f1a6145f804) - [Ensure interleave nested declarations have a semicolon when needed](https://redirect.github.com/parcel-bundler/lightningcss/commit/9e04c0112da0d614a437ff5903066607c50bc6f9) - [Fix casing for camel-cased svg values](https://redirect.github.com/parcel-bundler/lightningcss/pull/1108) - [Improve grid-template-areas handling and grid shorthand](https://redirect.github.com/parcel-bundler/lightningcss/pull/1132) - [Fix background-position minification and handling for various cases](https://redirect.github.com/parcel-bundler/lightningcss/pull/1124) - [Update browser compat data](https://redirect.github.com/parcel-bundler/lightningcss/commit/7754bd22ee5ad2c2be3b8c10ea3d24ed33d6dad7) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 9am on monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/csskit/csskit).  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

This code wasn't very DRY, which I don't really care about too much normally, but considering this change is sensitive logic it's worth removing duplicate logic here.

- releases: cargo publish before npm publish - releases: cargo publish last

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Comparing changes

Open a pull request

Commits on Jan 22, 2026

Commits on Jan 23, 2026

Commits on Jan 25, 2026

Commits on Jan 26, 2026

Commits on Jan 28, 2026

This comparison is taking too long to generate.

Uh oh!