Update lightningcss 1.22.0 → 1.22.1 (patch)

[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 (1.22.0 → 1.22.1) · Repo

Release Notes

1.22.1

• Init Wasm module only once in browsers – #615
• Update compat data – e255210
• Fix empty :is() when compiling nesting – b4bbe47

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

Commits

See the full diff on Github. The new version differs by 16 commits:

• downgrade napi for now
• v1.22.1
• Fix empty :is() when compiling nesting
• Update compat data
• update dependencies
• Init Wasm module only once in browsers (#615)
• Merge branch 'master' of github.com:parcel-bundler/parcel-css
• Publish crates
• fix: Remove `unsafe` in `derive(IntoOwned)` (#614)
• Move static_self dep behind feature flag
• Add missing descriptions
• release crates
• feat: Implement `IntoOwned` for more types (#599)
• release crates
• feat: Add `IntoOwned` trait (#597)
• Remove nesting option from playground, update docs

---

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)

[thecrypticace]

Seems like there are some regressions with respect to merging rules and outputting minified colors. Will need to look into these before merging. I'm guessing it's related to the compatibility data update.