Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps-dev): bump lightningcss from 1.16.0 to 1.19.0 #1779

Merged
merged 2 commits into from
Jul 24, 2023

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 14, 2023

Bumps lightningcss from 1.16.0 to 1.19.0.

Release notes

Sourced from lightningcss's releases.

v1.19.0

This release includes several features and improvements for the custom visitor API, including support for defining how to parse custom at rules. In addition, lots of bug fixes are included for auto prefixing, selector downleveling, and more.

Custom at-rules

When Lightning CSS does not know how to parse an unknown at rule, it stores the prelude and body as a list of raw tokens. Without a definition for how a rule should be parsed, Lighting CSS doesn't know how to interpret it. Tokens are fine for simple use cases, but if you are building a custom visitor plugin that processes a custom at-rule, and want it to integrate with the rest of CSS, it is useful to define how the rule should be parsed and interpreted. In this release, a new customAtRules option has been added to the API to enable just that.

For example, here is how you could define an @mixin rule which expects a custom identifier as its prelude, and a style-block as its body. This allows nesting declarations and rules just like other at-rules like @media and @supports.

{
  customAtRules: {
    mixin: {
      prelude: '<custom-ident>',
      body: 'style-block'
    }
  }
}

With that, you can parse code like this:

@mixin foo {
  color: red;
&.bar {
color: green;
}
}

Lightning CSS also validates the code and will emit syntax errors when it doesn't conform to the syntax definition. Another nice part is that we use this definition to automatically infer the TypeScript types for these rules when used in custom visitors.

Check out the documentation to learn more!

Features

  • Implement support for parsing custom at rules in JS bindings (#395)
  • Support raw property on returned declarations in visitors (#385)
  • Support raw values in visitors that return tokens (f9ed30f9ed8399d1599a9724eb55ce7e0c0ee8ba)
  • Make more AST properties optional in visitor return types (3fc05a9af629b69b72eaf5371891961d93450a1d)
  • Add substitute_variables function to UnparsedProperty in the Rust API (#388)
  • Add Implement Property::set_prefix function (a19228dcda0cc0fa6a98f1c9ab19829d9f8c0584)
  • Merge non-adjacent @layer rules (6419d542bad89b4f64dcf5a2f481a4e6b6d8a7a9)
  • Short-circuit on error in Rust visitor API (#406)
  • Support nesting selector at the root, which is transformed to :scope (44434116f4a0f0182a041971028b6cc729ecadc4)

... (truncated)

Commits
  • f2a7c8f Bump node version in CI
  • da3cb9a v1.19.0
  • f394b50 Use unpkg module option in docs for wasm
  • fcf4127 Fix serializing currentColor
  • f9ed30f Support raw values in visitors that return tokens
  • 6a53944 Fix cue-region-function ast
  • 331c8a9 Improve deserialization error messages
  • 856d460 Copy license into all npm packages
  • 482fc40 Fix serializing :host and ::slotted
  • 31fc453 Fix downleveling selectors
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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)
> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [lightningcss](https://github.com/parcel-bundler/lightningcss) from 1.16.0 to 1.19.0.
- [Release notes](https://github.com/parcel-bundler/lightningcss/releases)
- [Commits](parcel-bundler/lightningcss@v1.16.0...v1.19.0)

---
updated-dependencies:
- dependency-name: lightningcss
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Feb 14, 2023

The following labels could not be found: dependencies.

@Yucohny Yucohny merged commit 9cc64ed into cn Jul 24, 2023
1 of 6 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/lightningcss-1.19.0 branch July 24, 2023 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant