chore(deps): update dependency lightningcss to v1.28.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lightningcss	1.23.0 -> 1.28.1

---

Release Notes

parcel-bundler/lightningcss (lightningcss)

v1.28.1

Compare Source

v1.28.0

Compare Source

Added

• Add option to avoid hashing @container names in CSS Modules by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/835
• Improve error message of input:placeholder by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/813
• Add an error for the deprecated @value at-rule of CSS Modules by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/842

Fixed

• Don't panic when passing system-color to color-mix by @​inottn in https://github.com/parcel-bundler/lightningcss/pull/819
• Dependency updates by @​kornelski in https://github.com/parcel-bundler/lightningcss/pull/814
• Fix order of fallback width, height, and other size related properties – 22a8b6f
• Fix stack overflow parsing calc expression – e3c8e12
• Fix crash when parsing an invalid calc expression – 378955e
• Skip clamp function reduction when the comparison between preferred and max value is unknown – ddc9ce8
• Update browser compatibility data – f6b033f
• docs: Update help command docs by @​DylanPiercey in https://github.com/parcel-bundler/lightningcss/pull/812
• docs: fix link to visitor type definitions by @​mayank99 in https://github.com/parcel-bundler/lightningcss/pull/823

v1.27.0

Compare Source

Added

• Add [content-hash] css module pattern by @​rubberpants in https://github.com/parcel-bundler/lightningcss/pull/802. This includes a hash of the file contents rather than the file path (as [hash] works), which can be used to support multiple versions of the same library simultaneously without conflicts.
• Improve error message for pseudo elements followed by selectors by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/797
• Implement pure mode lints for CSS Modules by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/796. This option enforces the use of a class or id selector in each rule.

Fixed

• Fix box-shadow combination of oklch and currentColor by @​hi-ogawa in https://github.com/parcel-bundler/lightningcss/pull/801
• Add missing browserslist import in docs.md by @​cpeaustriajc in https://github.com/parcel-bundler/lightningcss/pull/798
• Update broken selectors link in homepage by @​20jasper in https://github.com/parcel-bundler/lightningcss/pull/750
• Make CLI example work with Windows by @​tim-we in https://github.com/parcel-bundler/lightningcss/pull/726
• Update copyright year on main page by @​log101 in https://github.com/parcel-bundler/lightningcss/pull/790
• Update browser compat data - parcel-bundler/lightningcss@54390b4

v1.26.0

Compare Source

Added

• Add support for named timeline ranges in @keyframes by @​grimsteel in https://github.com/parcel-bundler/lightningcss/pull/787
• Implement animation-range properties – parcel-bundler/lightningcss@39964f1
• Add a lint for unsupported CSS Module selector by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/784
• add wasm file to package exports by @​elevatebart in https://github.com/parcel-bundler/lightningcss/pull/755
• Add support for arm64 Windows – parcel-bundler/lightningcss@0bcd896

Fixed

• Fix codegen of :is(input:checked) by @​kdy1 in https://github.com/parcel-bundler/lightningcss/pull/783
• Bump browserslist-rs 0.16.0 by @​chenjiahan in https://github.com/parcel-bundler/lightningcss/pull/772
• update compat data – parcel-bundler/lightningcss@dcbb997

v1.25.1

Compare Source

Fixes a property ordering bug when using the all shorthand.

v1.25.0

Compare Source

This release adds more granular options for CSS modules, implements some new CSS properties, and fixes bugs.

Added

• Add granular options to control which identifiers are scoped in CSS modules. You can turn off scoping for grid, animation, and custom_idents. This may be useful when migrating from other tools. See docs. Thanks @​timneutkens! 83839a9
• Optimize the all shorthand property to reset other properties except direction and unicode-bidi. d7aeff3
• Implement animation-timeline property and add support for it in the animation shorthand f4408c7

Fixed

• Prevent simplifying translate: none and scale: none which are distinct from translate: 0 and scale: 1. Thanks @​RobinMalfait! a4cc024
• Fix crash on box-shadow with currentColor keyword. Thanks @​magic-akari! 06ba62f
• Fix minifier removing zero channels in color() function to follow spec change 445def9
• Fix CSS module scoping with variables in animation shorthand fb4b334
• Update browser compatibility data ec9da43

v1.24.1

Compare Source

• Disabled CSS transform optimizations using matrix(), which could break transitions and animations. – https://github.com/parcel-bundler/lightningcss/pull/694
• Merge @supports declarations with the same property (minus vendor prefix) and value – 6bd2761

v1.24.0

Compare Source

This release adds support the the light-dark() color function, parses CSS system colors, deduplicates custom properties during minification, merges duplicates @keyframes rules, and fixes some bugs.

light-dark()

The light-dark() function allows you to specify a light mode and dark mode color in a single declaration, without needing to write a separate media query rule. In addition, it uses the color-scheme property to control which theme to use, which allows you to set it programmatically. The color-scheme property also inherits so themes can be nested and the nearest ancestor color scheme applies.

Lightning CSS converts the light-dark() function to use CSS variable fallback when your browser targets don't support it natively. For this to work, you must set the color-scheme property on an ancestor element. The following example shows how you can support both operating system and programmatic overrides for the color scheme.

html {
  color-scheme: light dark;
}

html[data-theme=light] {
  color-scheme: light;
}

html[data-theme=dark] {
  color-scheme: dark;
}

button {
  background: light-dark(#aaa, #​444);
}

compiles to:

html {
  --lightningcss-light: initial;
  --lightningcss-dark: ;
  color-scheme: light dark;
}

@​media (prefers-color-scheme: dark) {
  html {
    --lightningcss-light: ;
    --lightningcss-dark: initial;
  }
}

html[data-theme="light"] {
  --lightningcss-light: initial;
  --lightningcss-dark: ;
  color-scheme: light;
}

html[data-theme="dark"] {
  --lightningcss-light: ;
  --lightningcss-dark: initial;
  color-scheme: dark;
}

button {
  background: var(--lightningcss-light, #aaa) var(--lightningcss-dark, #​444);
}

Check it out in the playground.

CSS system colors

CSS system colors are now supported during parsing, meaning they can be safely deduplicated when merging rules.

.a {
  background: Highlight;
}

.a {
  background: ButtonText;
}

compiles to:

.a{background:buttontext}

Custom property deduplication

CSS custom properties are now deduplicated when merging rules. The last property value always wins.

.a {
  --foo: red;
}

.a {
  --foo: green;
}

minifies to:

.a{--foo:green}

@keyframes deduplication

@keyframes rules are also now deduplicated during minification. The last rule of the same name wins.

@​keyframes a {
  from { opacity: 0 }
  to { opacity: 1 }
}

@​keyframes a {
  from { color: red }
  to { color: blue }
}

compiles to:

@​keyframes a{0%{color:red}to{color:#​00f}}

Other bug fixes

• Bump browserslist-rs and browser compat data
• Don't output duplicate properties when incompatible with targets
• Parse a TokenList instead of only a single Token in @property rules

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e736cde

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR