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

chore(deps): update all non-major dependencies #52

Merged
merged 1 commit into from
Aug 11, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/vscode (source) 1.80.0 -> 1.81.0 age adoption passing confidence
esbuild ^0.18.19 -> ^0.18.20 age adoption passing confidence

Release Notes

evanw/esbuild (esbuild)

v0.18.20

Compare Source

  • Support advanced CSS @import rules (#​953, #​3137)

    CSS @import statements have been extended to allow additional trailing tokens after the import path. These tokens sort of make the imported file behave as if it were wrapped in a @layer, @supports, and/or @media rule. Here are some examples:

    @​import url(foo.css);
    @​import url(foo.css) layer;
    @​import url(foo.css) layer(bar);
    @​import url(foo.css) layer(bar) supports(display: flex);
    @​import url(foo.css) layer(bar) supports(display: flex) print;
    @​import url(foo.css) layer(bar) print;
    @​import url(foo.css) supports(display: flex);
    @​import url(foo.css) supports(display: flex) print;
    @​import url(foo.css) print;

    You can read more about this advanced syntax here. With this release, esbuild will now bundle @import rules with these trailing tokens and will wrap the imported files in the corresponding rules. Note that this now means a given imported file can potentially appear in multiple places in the bundle. However, esbuild will still only load it once (e.g. on-load plugins will only run once per file, not once per import).


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Aug 11, 2023

Codecov Report

Merging #52 (280a94d) into main (6311f48) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   87.50%   87.50%           
=======================================
  Files           1        1           
  Lines          24       24           
  Branches        3        3           
=======================================
  Hits           21       21           
  Partials        3        3           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@renovate renovate bot merged commit ec504bf into main Aug 11, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch August 11, 2023 08:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants