Skip to content

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

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

Merged
merged 1 commit into from
Jul 24, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^18.16.19 -> ^18.17.0 age adoption passing confidence
carbon-components-svelte ^0.77.0 -> ^0.78.0 age adoption passing confidence
carbon-icons-svelte ^12.0.0 -> ^12.1.0 age adoption passing confidence
carbon-preprocess-svelte ^0.9.1 -> ^0.10.0 age adoption passing confidence
esbuild ^0.18.14 -> ^0.18.16 age adoption passing confidence
eslint-plugin-svelte (source) ^2.32.2 -> ^2.32.4 age adoption passing confidence
pnpm (source) 8.6.9 -> 8.6.10 age adoption passing confidence
postcss (source) ^8.4.26 -> ^8.4.27 age adoption passing confidence
sass ^1.63.6 -> ^1.64.1 age adoption passing confidence
svelte (source) ^4.0.5 -> ^4.1.1 age adoption passing confidence
vite (source) ^4.4.4 -> ^4.4.6 age adoption passing confidence

Release Notes

carbon-design-system/carbon-components-svelte (carbon-components-svelte)

v0.78.0

Compare Source

⚠ BREAKING CHANGES
  • typescript: minimum Svelte version for TypeScript users is 3.55
Features
carbon-design-system/carbon-icons-svelte (carbon-icons-svelte)

v12.1.0

Compare Source

Features

  • support Svelte version 4; minimum Svelte version required for TypeScript users is now 3.55
carbon-design-system/carbon-preprocess-svelte (carbon-preprocess-svelte)

v0.10.0

Compare Source

Breaking Changes

  • upgrade svelte-preprocess from v4.10.7 to v5.0.3 to support TypeScript 5

Fixes

  • support carbon-icons-svelte@12
evanw/esbuild (esbuild)

v0.18.16

Compare Source

  • Fix a regression with whitespace inside :is() (#​3265)

    The change to parse the contents of :is() in version 0.18.14 introduced a regression that incorrectly flagged the contents as a syntax error if the contents started with a whitespace token (for example div:is( .foo ) {}). This regression has been fixed.

v0.18.15

Compare Source

  • Add the --serve-fallback= option (#​2904)

    The web server built into esbuild serves the latest in-memory results of the configured build. If the requested path doesn't match any in-memory build result, esbuild also provides the --servedir= option to tell esbuild to serve the requested path from that directory instead. And if the requested path doesn't match either of those things, esbuild will either automatically generate a directory listing (for directories) or return a 404 error.

    Starting with this release, that last step can now be replaced with telling esbuild to serve a specific HTML file using the --serve-fallback= option. This can be used to provide a "not found" page for missing URLs. It can also be used to implement a single-page app that mutates the current URL and therefore requires the single app entry point to be served when the page is loaded regardless of whatever the current URL is.

  • Use the tsconfig field in package.json during extends resolution (#​3247)

    This release adds a feature from TypeScript 3.2 where if a tsconfig.json file specifies a package name in the extends field and that package's package.json file has a tsconfig field, the contents of that field are used in the search for the base tsconfig.json file.

  • Implement CSS nesting without :is() when possible (#​1945)

    Previously esbuild would always produce a warning when transforming nested CSS for a browser that doesn't support the :is() pseudo-class. This was because the nesting transform needs to generate an :is() in some complex cases which means the transformed CSS would then not work in that browser. However, the CSS nesting transform can often be done without generating an :is(). So with this release, esbuild will no longer warn when targeting browsers that don't support :is() in the cases where an :is() isn't needed to represent the nested CSS.

    In addition, esbuild's nested CSS transform has been updated to avoid generating an :is() in cases where an :is() is preferable but there's a longer alternative that is also equivalent. This update means esbuild can now generate a combinatorial explosion of CSS for complex CSS nesting syntax when targeting browsers that don't support :is(). This combinatorial explosion is necessary to accurately represent the original semantics. For example:

    /* Original code */
    .first,
    .second,
    .third {
      & > & {
        color: red;
      }
    }
    
    /* Old output (with --target=chrome80) */
    :is(.first, .second, .third) > :is(.first, .second, .third) {
      color: red;
    }
    
    /* New output (with --target=chrome80) */
    .first > .first,
    .first > .second,
    .first > .third,
    .second > .first,
    .second > .second,
    .second > .third,
    .third > .first,
    .third > .second,
    .third > .third {
      color: red;
    }

    This change means you can now use CSS nesting with esbuild when targeting an older browser that doesn't support :is(). You'll now only get a warning from esbuild if you use complex CSS nesting syntax that esbuild can't represent in that older browser without using :is(). There are two such cases:

    /* Case 1 */
    a b {
      .foo & {
        color: red;
      }
    }
    
    /* Case 2 */
    a {
      > b& {
        color: red;
      }
    }

    These two cases still need to use :is(), both for different reasons, and cannot be used when targeting an older browser that doesn't support :is():

    /* Case 1 */
    .foo :is(a b) {
      color: red;
    }
    
    /* Case 2 */
    a > a:is(b) {
      color: red;
    }
  • Automatically lower inset in CSS for older browsers

    With this release, esbuild will now automatically expand the inset property to the top, right, bottom, and left properties when esbuild's target is set to a browser that doesn't support inset:

    /* Original code */
    .app {
      position: absolute;
      inset: 10px 20px;
    }
    
    /* Old output (with --target=chrome80) */
    .app {
      position: absolute;
      inset: 10px 20px;
    }
    
    /* New output (with --target=chrome80) */
    .app {
      position: absolute;
      top: 10px;
      right: 20px;
      bottom: 10px;
      left: 20px;
    }
  • Add support for the new @starting-style CSS rule (#​3249)

    This at rule allow authors to start CSS transitions on first style update. That is, you can now make the transition take effect when the display property changes from none to block.

    /* Original code */
    @​starting-style {
      h1 {
        background-color: transparent;
      }
    }
    
    /* Output */
    @​starting-style{h1{background-color:transparent}}

    This was contributed by @​yisibl.

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v2.32.4

Compare Source

Patch Changes

v2.32.3

Compare Source

Patch Changes
pnpm/pnpm (pnpm)

v8.6.10

Compare Source

Patch Changes

  • Installation succeeds if a non-optional dependency of an optional dependency has failing installation scripts #​6822.
  • The length of the temporary file names in the content-addressable store reduced in order to prevent ENAMETOOLONG errors from happening #​6842.
  • Ignore empty patch content when patch-commit.
  • Sort keys in packageExtensions before calculating packageExtensionsChecksum #​6824.
  • Pass the right scheme to git ls-remote in order to prevent a fallback to git+ssh that would result in a 'host key verification failed' issue #​6806
  • The "postpublish" script of a git-hosted dependency is not executed, while building the dependency #​6822.

Our Gold Sponsors

Our Silver Sponsors

postcss/postcss (postcss)

v8.4.27

Compare Source

  • Fixed Container clone methods types.
sass/dart-sass (sass)

v1.64.1

Compare Source

Embedded Sass
  • Fix a bug where a valid SassCalculation.clamp() with less than 3 arguments
    would throw an error.

v1.64.0

Compare Source

  • Comments that appear before or between @use and @forward rules are now
    emitted in source order as much as possible, instead of always being emitted
    after the CSS of all module dependencies.

  • Fix a bug where an interpolation in a custom property name crashed if the file
    was loaded by a @use nested in an @import.

JavaScript API
  • Add a new SassCalculation type that represents the calculation objects added
    in Dart Sass 1.40.0.

  • Add Value.assertCalculation(), which returns the value if it's a
    SassCalculation and throws an error otherwise.

  • Produce a better error message when an environment that supports some Node.js
    APIs loads the browser entrypoint but attempts to access the filesystem.

Embedded Sass
  • Fix a bug where nested relative @imports failed to load when using the
    deprecated functions render or renderSync and those relative imports were
    loaded multiple times across different files.
sveltejs/svelte (svelte)

v4.1.1

Compare Source

Patch Changes
  • fix: svelte:component spread props change not picked up (#​9006)

v4.1.0

Compare Source

Minor Changes
  • feat: add ability to extend custom element class (#​8991)
Patch Changes
  • fix: ensure svelte:component evaluates props once (#​8946)

  • fix: remove let:variable slot bindings from select binding dependencies (#​8969)

  • fix: handle destructured primitive literals (#​8871)

  • perf: optimize imports that are not mutated or reassigned (#​8948)

  • fix: don't add accessor twice (#​8996)

vitejs/vite (vite)

v4.4.6

Compare Source

v4.4.5

Compare Source


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5e0d36b to 77b6820 Compare July 24, 2023 11:30
@dominikg dominikg merged commit cb01480 into main Jul 24, 2023
@dominikg dominikg deleted the renovate/all-minor-patch branch July 24, 2023 11:53
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.

1 participant