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 #985

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@fontsource/fira-mono (source) ^5.0.15 -> ^5.1.0 age adoption passing confidence
@sveltejs/adapter-auto (source) ^3.2.4 -> ^3.2.5 age adoption passing confidence
@sveltejs/adapter-auto (source) 3.2.4 -> 3.2.5 age adoption passing confidence
@sveltejs/adapter-node (source) ^5.2.2 -> ^5.2.3 age adoption passing confidence
@sveltejs/eslint-config (source) ^8.0.1 -> ^8.1.0 age adoption passing confidence
@sveltejs/kit (source) ^2.5.26 -> ^2.5.28 age adoption passing confidence
@sveltejs/package (source) ^2.3.4 -> ^2.3.5 age adoption passing confidence
eslint-plugin-n ^17.10.2 -> ^17.10.3 age adoption passing confidence
eslint-plugin-svelte (source) ^2.43.0 -> ^2.44.0 age adoption passing confidence
express (source) ^4.20.0 -> ^4.21.0 age adoption passing confidence
husky ^9.1.5 -> ^9.1.6 age adoption passing confidence
npm-run-all2 ^6.2.2 -> ^6.2.3 age adoption passing confidence
playwright-core (source) ~1.47.0 -> ~1.47.1 age adoption passing confidence
postcss (source) ^8.4.45 -> ^8.4.47 age adoption passing confidence
publint (source) ^0.2.10 -> ^0.2.11 age adoption passing confidence
sass ^1.78.0 -> ^1.79.1 age adoption passing confidence
serve-static ^1.16.0 -> ^1.16.2 age adoption passing confidence
svelte (source) ^5.0.0-next.244 -> ^5.0.0-next.250 age adoption passing confidence
svelte-check ^4.0.1 -> ^4.0.2 age adoption passing confidence
svelte-eslint-parser ^0.41.0 -> ^0.41.1 age adoption passing confidence
typescript-eslint (source) ^8.5.0 -> ^8.6.0 age adoption passing confidence
vite (source) ^5.4.4 -> ^5.4.6 age adoption passing confidence
vitest (source) ^2.0.5 -> ^2.1.1 age adoption passing confidence

Release Notes

fontsource/font-files (@​fontsource/fira-mono)

v5.1.0

Compare Source

sveltejs/kit (@​sveltejs/adapter-auto)

v3.2.5

Compare Source

Patch Changes
sveltejs/kit (@​sveltejs/adapter-node)

v5.2.3

Compare Source

Patch Changes
sveltejs/eslint-config (@​sveltejs/eslint-config)

v8.1.0

Compare Source

Minor Changes
  • feat: add rule to enforce that process is imported (#​40)
sveltejs/kit (@​sveltejs/kit)

v2.5.28

Compare Source

Patch Changes
  • fix: import node:process instead of using globals (#​12641)

v2.5.27

Compare Source

Patch Changes
  • fix: asynchronously instantiate components when using Svelte 5 (#​12613)

  • fix: use {@​render ...} tag when generating default fallback page for svelte 5 apps (#​12653)

  • fix: emulate event.platform even when the route does not exist (#​12513)

sveltejs/kit (@​sveltejs/package)

v2.3.5

Compare Source

Patch Changes
  • fix: use input tsconfig when calling emitDts (#​12612)

  • chore(deps): update dependency chokidar to v4 (#​12671)

eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.10.3

Compare Source

🩹 Fixes
  • Use our data set to work out if a module is a node module (#​338) (6a1b2c5)
📚 Documentation
sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v2.44.0

Compare Source

Minor Changes
Patch Changes
expressjs/express (express)

v4.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: expressjs/express@4.20.0...4.21.0

typicode/husky (husky)

v9.1.6

Compare Source

bcomnes/npm-run-all2 (npm-run-all2)

v6.2.3

Compare Source

Commits
  • Merge pull request #​151 from bcomnes/fix-pnpm-agian c43fa2b
  • Avoid passing config fields as flags for pnpm dc2d7da
microsoft/playwright (playwright-core)

v1.47.1

Compare Source

postcss/postcss (postcss)

v8.4.47

Compare Source

  • Removed debug code.

v8.4.46

Compare Source

  • Fixed Cannot read properties of undefined (reading 'before').
bluwy/publint (publint)

v0.2.11

Compare Source

Features
New Contributors

Full Changelog: bluwy/publint@v0.2.10...v0.2.11

sass/dart-sass (sass)

v1.79.1

Compare Source

  • No user-visible changes.

v1.79.0

Compare Source

  • Breaking change: Passing a number with unit % to the $alpha parameter
    of color.change(), color.adjust(), change-color(), and adjust-color()
    is now interpreted as a percentage, instead of ignoring the unit. For example,
    color.change(red, $alpha: 50%) now returns rgb(255 0 0 / 0.5).

  • Potentially breaking compatibility fix: Sass no longer rounds RGB channels
    to the nearest integer. This means that, for example, rgb(0 0 1) != rgb(0 0 0.6). This matches the latest version of the CSS spec and browser behavior.

  • Potentially breaking compatibility fix: Passing large positive or negative
    values to color.adjust() can now cause a color's channels to go outside that
    color's gamut. In most cases this will currently be clipped by the browser and
    end up showing the same color as before, but once browsers implement gamut
    mapping it may produce a different result.

  • Add support for CSS Color Level 4 color spaces. Each color value now tracks
    its color space along with the values of each channel in that color space.
    There are two general principles to keep in mind when dealing with new color
    spaces:

    1. With the exception of legacy color spaces (rgb, hsl, and hwb), colors
      will always be emitted in the color space they were defined in unless
      they're explicitly converted.

    2. The color.to-space() function is the only way to convert a color to
      another color space. Some built-in functions may do operations in a
      different color space, but they'll always convert back to the original space
      afterwards.

  • rgb colors can now have non-integer channels and channels outside the normal
    gamut of 0-255. These colors are always emitted using the rgb() syntax so
    that modern browsers that are being displayed on wide-gamut devices can
    display the most accurate color possible.

  • Add support for all the new color syntax defined in Color Level 4, including:

    • oklab(), oklch(), lab(), and lch() functions;
    • a top-level hwb() function that matches the space-separated CSS syntax;
    • and a color() function that supports the srgb, srgb-linear,
      display-p3, a98-rgb, prophoto-rgb, rec2020, xyz, xyz-d50, and
      xyz-d65 color spaces.
  • Add new functions for working with color spaces:

    • color.to-space($color, $space) converts $color to the given $space. In
      most cases this conversion is lossless—the color may end up out-of-gamut for
      the destination color space, but browsers will generally display it as best
      they can regardless. However, the hsl and hwb spaces can't represent
      out-of-gamut colors and so will be clamped.

    • color.channel($color, $channel, $space: null) returns the value of the
      given $channel in $color, after converting it to $space if necessary.
      It should be used instead of the old channel-specific functions such as
      color.red() and color.hue().

    • color.same($color1, $color2) returns whether two colors represent the same
      color even across color spaces. It differs from $color1 == $color2 because
      == never consider colors in different (non-legacy) spaces as equal.

    • color.is-in-gamut($color, $space: null) returns whether $color is
      in-gamut for its color space (or $space if it's passed).

    • color.to-gamut($color, $space: null) returns $color constrained to its
      space's gamut (or to $space's gamut, if passed). This is generally not
      recommended since even older browsers will display out-of-gamut colors as
      best they can, but it may be necessary in some cases.

    • color.space($color): Returns the name of $color's color space.

    • color.is-legacy($color): Returns whether $color is in a legacy color
      space (rgb, hsl, or hwb).

    • color.is-powerless($color, $channel, $space: null): Returns whether the
      given $channel of $color is powerless in $space (or its own color
      space). A channel is "powerless" if its value doesn't affect the way the
      color is displayed, such as hue for a color with 0 chroma.

    • color.is-missing($color, $channel): Returns whether $channel's value is
      missing in $color. Missing channels can be explicitly specified using the
      special value none and can appear automatically when color.to-space()
      returns a color with a powerless channel. Missing channels are usually
      treated as 0, except when interpolating between two colors and in
      color.mix() where they're treated as the same value as the other color.

  • Update existing functions to support color spaces:

    • hsl() and color.hwb() no longer forbid out-of-bounds values. Instead,
      they follow the CSS spec by clamping them to within the allowed range.

    • color.change(), color.adjust(), and color.scale() now support all
      channels of all color spaces. However, if you want to modify a channel
      that's not in $color's own color space, you have to explicitly specify the
      space with the $space parameter. (For backwards-compatibility, this
      doesn't apply to legacy channels of legacy colors—for example, you can still
      adjust an rgb color's saturation without passing $space: hsl).

    • color.mix() and color.invert() now support the standard CSS algorithm
      for interpolating between two colors (the same one that's used for gradients
      and animations). To use this, pass the color space to use for interpolation
      to the $method parameter. For polar color spaces like hsl and oklch,
      this parameter also allows you to specify how hue interpolation is handled.

    • color.complement() now supports a $space parameter that indicates which
      color space should be used to take the complement.

    • color.grayscale() now operates in the oklch space for non-legacy colors.

    • color.ie-hex-str() now automatically converts its color to the rgb space
      and gamut-maps it so that it can continue to take colors from any color
      space.

  • The following functions are now deprecated, and uses should be replaced with
    the new color-space-aware functions defined above:

    • The color.red(), color.green(), color.blue(), color.hue(),
      color.saturation(), color.lightness(), color.whiteness(), and
      color.blackness() functions, as well as their global counterparts, should
      be replaced with calls to color.channel().

    • The global adjust-hue(), saturate(), desaturate(), lighten(),
      darken(), transaprentize(), fade-out(), opacify(), and fade-in()
      functions should be replaced by color.adjust() or color.scale().

  • Add a global-builtin future deprecation, which can be opted-into with the
    --future-deprecation flag or the futureDeprecations option in the JS or
    Dart API. This emits warnings when any global built-in functions that are
    now available in sass: modules are called. It will become active by default
    in an upcoming release alongside the @import deprecation.

Dart API
  • Added a ColorSpace class which represents the various color spaces defined
    in the CSS spec.

  • Added SassColor.space which returns a color's color space.

  • Added SassColor.channels and .channelsOrNull which returns a list
    of channel values, with missing channels converted to 0 or exposed as null,
    respectively.

  • Added SassColor.isLegacy, .isInGamut, .channel(), .isChannelMissing(),
    .isChannelPowerless(), .toSpace(), .toGamut(), .changeChannels(), and
    .interpolate() which do the same thing as the Sass functions of the
    corresponding names.

  • SassColor.rgb() now allows out-of-bounds and non-integer arguments.

  • SassColor.hsl() and .hwb() now allow out-of-bounds arguments.

  • Added SassColor.hwb(), .srgb(), .srgbLinear(), .displayP3(),
    .a98Rgb(), .prophotoRgb(), .rec2020(), .xyzD50(), .xyzD65(),
    .lab(), .lch(), .oklab(), .oklch(), and .forSpace() constructors.

  • Deprecated SassColor.red, .green, .blue, .hue, .saturation,
    .lightness, .whiteness, and .blackness in favor of
    SassColor.channel().

  • Deprecated SassColor.changeRgb(), .changeHsl(), and .changeHwb() in
    favor of SassColor.changeChannels().

  • Added SassNumber.convertValueToUnit() as a shorthand for
    SassNumber.convertValue() with a single numerator.

  • Added InterpolationMethod and HueInterpolationMethod which collectively
    represent the method to use to interpolate two colors.

JS API
  • While the legacy API has been deprecated since we released the modern API, we
    now emit warnings when the legacy API is used to make sure users are aware
    that it will be removed in Dart Sass 2.0.0. In the meantime, you can silence
    these warnings by passing legacy-js-api in silenceDeprecations when using
    the legacy API.

  • Modify SassColor to accept a new space option, with support for all the
    new color spaces defined in Color Level 4.

  • Add SassColor.space which returns a color's color space.

  • Add SassColor.channels and .channelsOrNull which returns a list of channel
    values, with missing channels converted to 0 or exposed as null, respectively.

  • Add SassColor.isLegacy, .isInGamut(), .channel(), .isChannelMissing(),
    .isChannelPowerless(), .toSpace(), .toGamut(), .change(), and
    .interpolate() which do the same thing as the Sass functions of the
    corresponding names.

  • Deprecate SassColor.red, .green, .blue, .hue, .saturation,
    .lightness, .whiteness, and .blackness in favor of
    SassColor.channel().

Embedded Sass
  • Add Color SassScript value, with support for all the new color spaces
    defined in Color Level 4.

  • Remove RgbColor, HslColor and HwbColor SassScript values.

expressjs/serve-static (serve-static)

v1.16.2

Compare Source

v1.16.1

Compare Source

sveltejs/svelte (svelte)

v5.0.0-next.250

Compare Source

Patch Changes
  • fix: correctly migrate sequence expressions (#​13291)

  • fix: avoid disconnecting deriveds that are still active (#​13292)

  • feat: Add accessibility warnings for buttons and anchors without explicit labels and content (#​13130)

v5.0.0-next.249

Compare Source

Patch Changes
  • fix: ensure snapshot logs don't affect dependency graph (#​13286)

  • fix: allow custom element styles to be updated in HMR mode (#​13225)

  • fix: inject styles correctly when mounting inside an iframe (#​13225)

v5.0.0-next.248

Compare Source

Patch Changes
  • feat: provide guidance in browser console when logging $state objects (#​13142)

  • fix: ensure correct parent effect is associated with render effects (#​13274)

  • feat: unwrap function expressions where possible, and optimise bindings (#​13269)

v5.0.0-next.247

Compare Source

Patch Changes
  • fix: wait until template strings are complete before sanitizing (#​13262)

  • fix: avoid flushing sync with $inspect (#​13239)

  • fix: separate template_effect for dynamic class/style directive with dynamic attributes (#​13171)

  • fix: treat pure call expressions as potentially reactive if they reference local bindings (#​13264)

  • fix: follow spec for customElement option (#​13247)

  • fix: tighten up `# svelte prefix validation (#​13261)

v5.0.0-next.246

Compare Source

Patch Changes
  • perf: inline module variables into template (#​13075)

  • fix: allow custom element events on slot to bubble inside custom element (#​13222)

  • fix: add missing autocomplete attribute tokens (#​13229)

  • feat: add infinite loop effect callstack (#​13231)

v5.0.0-next.245

Compare Source

Patch Changes
  • fix: visit expression for svelte:component references (#​13151)

  • fix: ensure signal graph is consistent before triggering $inspect signals (#​13153)

  • feat: better types for the autocomplete attribute (#​13201)

  • fix: widen ownership upon property access if necessary (#​13175)

  • fix: don't show state_referenced_locally warning on types (#​13177)

  • fix: ensure locally mutated bindable props persist with spreading props (#​13190)

  • fix: try catch strict_equals to avoid error accessing STATE_SYMBOL (#​13216)

  • fix: ensure types are easier to follow for TypeScript (#​13140)

  • fix: ensure $inspect effects are fine-grain (#​13199)

  • fix: ensure unowned derived signals correctly re-connect to graph (#​13184)

  • fix: ensure inner script tags are properly removed (#​13152)

  • chore: improve ssr parent validation (#​13158)

  • fix: prevent nullish snippet for rendering empty content (#​13083)

  • fix: allow more characters in the unicode range as component identifiers (#​13198)

  • fix: allow for nesting selector in pseudoclasses (#​13209)

  • fix: ensure StyleDirective and ClassDirective are marked as dynamic (#​13205)

sveltejs/language-tools (svelte-check)

v4.0.2

Compare Source

  • fix: ensure components typed through Svelte 5's Component interface get proper intellisense
sveltejs/svelte-eslint-parser (svelte-eslint-parser)

v0.41.1

Compare Source

Patch Changes
typescript-eslint/typescript-eslint (typescript-eslint)

v8.6.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

vitejs/vite (vite)

v5.4.6

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.5

Compare Source

Please refer to CHANGELOG.md for details.

vitest-dev/vitest (vitest)

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 68b4834 to d8c06c7 Compare September 18, 2024 01:39
@dominikg dominikg merged commit 38fd166 into main Sep 18, 2024
6 checks passed
@dominikg dominikg deleted the renovate/all-minor-patch branch September 18, 2024 08:01
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