lightningcss
1.33.0 · 20 Jul 2026MPL-2.0259.9M / weekRepositoryHomepagenpmAtom feed
Upgrading lightningcss From 1.21.7 to 1.33.0
24 releases in betweennotes for 21
Reading releases, release notes and advisories…
- 1+
- change to make
- 0
- advisories fixed
- 46+
- new
- 76+
- fixes
Counted from 21 of 24 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking1.30.0
Release by release
- New
Add support for
::highlight - New
Add support for @position-try at-rule #851
- New
Add support for ::search-text and :current::search-text
- New
Collapse light-dark(x, x) to x
- New
- New
Enable custom resolvers to mark imports as external. Resolvers may now return
{external: string}to mark an import as external. This will leave the@importin the output CSS instead of bundling it. See the docs for details. - New
Allow visitors to add dependencies. Visitors may now be functions which receive an
addDependencyfunction as an option. Dependencies may be used by tools that call Lightning CSS such as bundlers to implement file watching or caching. See the docs for details. - New
- Fixed
- New
1.31.1no release note
- Fixed
- Fixed
- Fixed
1.30.1nothing new or fixed in the note
- Breaking
Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
- New
Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
- New
Skip generating unnecessary
@supportsrules when already nested in a@supportsrule – #878, d398c1b86439dfd243a6c2ba627a8e7981118a44 - New
Improve error recovery for media queries – #954
- Breaking
- New
Support for
::details-contentand::target-textselectors – @philipp-spiess - New
Support
/* cssmodules-pure-no-check */comments – @jantimon
- New
8 other lines we could not sort, mostly version bumps
- 1.29.3
Update
:placeholder-shownselector name across browsers – @Marukome0743 - 1.29.3
Update browser compatibility data – c03a7e7f7cfe7a8d487f9402e3194a1d732f9a04
- 1.29.2
Update detect-libc for better compatibility
- 1.29.2
Bump browserslist-rs 0.17.0
- 1.24.1
Disabled CSS
transformoptimizations usingmatrix(), which could break transitions and animations. – #694 - 1.24.1
Merge
@supportsdeclarations with the same property (minus vendor prefix) and value – 6bd2761badb9d5434783acffcae35ef6c3311e06 - 1.22.1
Init Wasm module only once in browsers – #615
- 1.22.1
Update compat data – e25521014691ebc13ee889a4ebf5b78f14ea1b6a
8 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.