Bump lightningcss from 1.20.0 to 1.21.5

[dependabot]

Bumps lightningcss from 1.20.0 to 1.21.5.

Release notes

Sourced from lightningcss's releases.

v1.21.5

Fixed node segmentation fault when throwing an error in a custom visitor using the bundleAsync API - parcel-bundler/lightningcss@50dad7f

v1.21.3

• Fix bundle options type

v1.21.2

Fixes

• Propagate error location info to JS in bundler APIs – 91ec8d3e6221973fe5bbb649ce1311c583b5bf2d
• Omit analyzeDependencies option from bundler APIs in TypeScript definitions – ae97aa1f79d27f72f20161b55dfd743567e04a3c
• Fix deduplicating multiple copies of the same rule – a8d909adcb3a4db67243a74e9058beb3be79cecd

v1.21.1

Fixes

• Ensure fallback rules for logical properties are before nested rules – e66d99cd9b41e4cb99c78db0f30fcf3323321c63
• Fix Safari compat data for ::marker pseudo element – cff779d78a7ea9639ed4c28059c19567d4814e0b
• Add compat data for ::part pseudo element – fbf0d247f4d30d24253e2e7642730a9545e57691
• Avoid splitting and vendor prefixing :is() when we can safely unwrap it – 8d94ea1da0e7b5112e2617ab84832f97c2fe4c0e
• Ensure split incompatible rules get the correct vendor prefix – d6e129538b13ad930b416ac94d1f37dc0640053d
• Add semicolon after declarations if preserving nesting – acde78b2fca6059fdf104013416b3dadb56e2af2
• Preserve license comments at the start of a stylesheet – 5cec8beb1e8d14fb1818f220db3d9354b7405506
• Do not crash on currentColor in color-mix() or relative color syntax – 20c9612694a0aeec0891a56819f690ac7de6e06a
• Specify exact version of lightningcss-derive in Rust crate – 1203368b722ef0c9dffb03e70245423e352f6cff

v1.21.0

This release includes new features to improve compatibility of output CSS with your browser targets, and safely remove old fallbacks that aren't needed anymore. It also gives you more control over exactly how CSS is compiled, and fixes some bugs.

Preserve manual fallbacks

Lightning CSS will now preserve manually provided fallback values when some of your browser targets do not support the last one. For example, in the following rule, if some targets didn't support the max function, both declarations would be preserved. Otherwise, if we are sure that all targets support it, Lightning CSS will drop the fallback declaration.

.foo {
  margin-right: 22px;
  margin-right: max(4%, 22px);
}

This is supported for many types of values such as lengths, colors, gradients, images, font styles, etc. It uses compatibility data from caniuse and MDN to determine if each value is supported.

Include and exclude options

You can now control exactly how Lightning CSS compiles using the "include" and "exclude" options, in addition to the existing "targets". This allows you to explicitly turn on or off certain features, which overrides the defaults based on the provided browser targets. For example, you might want to only compile colors, and handle auto prefixing or other features with another tool. Or you may want to handle everything except vendor prefixing with Lightning CSS. These options make that possible.

An enum of available feature flags is provided, and you can use the bitwise OR operator to combine flags together, e.g. Features.Nesting | Features.Colors. There are also some flags which turn on multiple other flags at once, e.g. Selectors, Colors, and MediaQueries. The playground has been updated to show these flags and includes checkboxes to turn them on or off.

import {transform, Features, browserslistToTargets} from 'lightningcss';
</tr></table> 

... (truncated)

Commits

• d44a73c v1.21.5
• 50dad7f Work around napi-rs crash when cloning an error
• bd517fd Actually don't omit analyzeDependencies from bundle options
• 83bab71 v1.21.3
• cd7a602 Fix bundle options type (#528)
• e4963a5 Setup wasm target
• c24270b Update rust toolchain
• 51be33c v1.21.2
• a8d909a Fix deduplicating multiple instances of a rule
• cc1aa63 Update GitHub Actions CI (#519)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: dependencies.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.