Update lightningcss-darwin-arm64 1.26.0 → 1.29.1 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ lightningcss-darwin-arm64 (1.26.0 → 1.29.1) · Repo

Release Notes

1.29.0

Added

• Implement view transitions level 2, including the @view-transition rule, view-transition-class and view-transition-group properties, and class selector features of the view transition pseudo elements. This enables CSS module scoping and better minification when using these features. – #885
• Support parsing the @font-feature-values rule – #840
• Add a feature flag to explicitly enable or disable transpiling the light-dark() function – 3043896

Fixed

• Compile media query range syntax with boolean logic instead of fractional pixels. Fixes issues with rounding certain values. – 7f29035
• Fix parsing the list-style shorthand property – 97891d8
• Fix hashing of :nth-child(an + b of X) selectors in CSS modules – ed9e659
• Update napi-rs to fix issue with \0 characters in filenames – 43707c3
• Fix CustomAtRule.loc TypeScript type – #876
• Call StyleSheet / StyleSheetExit / Rule.custom.* in visitors passed to composeVisitors – #875
• Update browser compat data – cdbf0d4

1.28.2

Fixes

• Fix duplicate prefixed properties in transition-property – #850 (thanks @RobinMalfait and @LeoniePhiline!)
• Fix mapping original name from source maps – 78f2fc4
• Bump browser compat data – 4159bc5
• Ensure consistent order of custom properties when all property is set – d4eec35

1.28.0

Added

• Add option to avoid hashing @container names in CSS Modules by @kdy1 in #835
• Improve error message of input:placeholder by @kdy1 in #813
• Add an error for the deprecated @value at-rule of CSS Modules by @kdy1 in #842

Fixed

• Don't panic when passing system-color to color-mix by @inottn in #819
• Dependency updates by @kornelski in #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 #812
• docs: fix link to visitor type definitions by @mayank99 in #823

Does any of this look wrong? Please let us know.

Sorry, we couldn't find anything useful about this release.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Sorry, but Depfu wasn't able to merge this PR. An error has been logged and we'll take a look at it.

[depfu]

Sorry, but Depfu wasn't able to merge this PR. An error has been logged and we'll take a look at it.

[depfu]

Sorry, but Depfu wasn't able to merge this PR. An error has been logged and we'll take a look at it.

[depfu]

Sorry, but Depfu wasn't able to merge this PR. An error has been logged and we'll take a look at it.