chore(deps): update all non-major dependencies #985
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^5.0.15
->^5.1.0
^3.2.4
->^3.2.5
3.2.4
->3.2.5
^5.2.2
->^5.2.3
^8.0.1
->^8.1.0
^2.5.26
->^2.5.28
^2.3.4
->^2.3.5
^17.10.2
->^17.10.3
^2.43.0
->^2.44.0
^4.20.0
->^4.21.0
^9.1.5
->^9.1.6
^6.2.2
->^6.2.3
~1.47.0
->~1.47.1
^8.4.45
->^8.4.47
^0.2.10
->^0.2.11
^1.78.0
->^1.79.1
^1.16.0
->^1.16.2
^5.0.0-next.244
->^5.0.0-next.250
^4.0.1
->^4.0.2
^0.41.0
->^0.41.1
^8.5.0
->^8.6.0
^5.4.4
->^5.4.6
^2.0.5
->^2.1.1
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
fix: import
node:process
instead of using globals (#12641)Updated dependencies [
e798ef718f163bed4f93e1918bd8294f765376ad
]:sveltejs/kit (@sveltejs/adapter-node)
v5.2.3
Compare Source
Patch Changes
fix: import
node:process
instead of using globals (#12641)Updated dependencies [
e798ef718f163bed4f93e1918bd8294f765376ad
]:sveltejs/eslint-config (@sveltejs/eslint-config)
v8.1.0
Compare Source
Minor Changes
sveltejs/kit (@sveltejs/kit)
v2.5.28
Compare Source
Patch Changes
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
📚 Documentation
sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)
v2.44.0
Compare Source
Minor Changes
85053a1
Thanks @jrmajor! - feat: add config option for foreign elements insvelte/html-self-closing
rulePatch Changes
690c04e
Thanks @ota-meshi! - fix: update svelte-eslint-parser to 0.41.1expressjs/express (express)
v4.21.0
Compare Source
What's Changed
"back"
magic string in redirects by @blakeembrey in https://github.com/expressjs/express/pull/5935New 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
c43fa2b
dc2d7da
microsoft/playwright (playwright-core)
v1.47.1
Compare Source
postcss/postcss (postcss)
v8.4.47
Compare Source
v8.4.46
Compare Source
Cannot read properties of undefined (reading 'before')
.bluwy/publint (publint)
v0.2.11
Compare Source
Features
formatMessage()
utility with a newcolor
option to force enable or disable returning color in string (https://github.com/bluwy/publint/pull/110)New Contributors
Full Changelog: bluwy/publint@v0.2.10...v0.2.11
sass/dart-sass (sass)
v1.79.1
Compare Source
v1.79.0
Compare Source
Breaking change: Passing a number with unit
%
to the$alpha
parameterof
color.change()
,color.adjust()
,change-color()
, andadjust-color()
is now interpreted as a percentage, instead of ignoring the unit. For example,
color.change(red, $alpha: 50%)
now returnsrgb(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 thatcolor'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:
With the exception of legacy color spaces (
rgb
,hsl
, andhwb
), colorswill always be emitted in the color space they were defined in unless
they're explicitly converted.
The
color.to-space()
function is the only way to convert a color toanother 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 normalgamut of 0-255. These colors are always emitted using the
rgb()
syntax sothat 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()
, andlch()
functions;hwb()
function that matches the space-separated CSS syntax;color()
function that supports thesrgb
,srgb-linear
,display-p3
,a98-rgb
,prophoto-rgb
,rec2020
,xyz
,xyz-d50
, andxyz-d65
color spaces.Add new functions for working with color spaces:
color.to-space($color, $space)
converts$color
to the given$space
. Inmost 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
andhwb
spaces can't representout-of-gamut colors and so will be clamped.
color.channel($color, $channel, $space: null)
returns the value of thegiven
$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()
andcolor.hue()
.color.same($color1, $color2)
returns whether two colors represent the samecolor 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
isin-gamut for its color space (or
$space
if it's passed).color.to-gamut($color, $space: null)
returns$color
constrained to itsspace's gamut (or to
$space
's gamut, if passed). This is generally notrecommended 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 colorspace (
rgb
,hsl
, orhwb
).color.is-powerless($color, $channel, $space: null)
: Returns whether thegiven
$channel
of$color
is powerless in$space
(or its own colorspace). 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 ismissing in
$color
. Missing channels can be explicitly specified using thespecial value
none
and can appear automatically whencolor.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()
andcolor.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()
, andcolor.scale()
now support allchannels 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 thespace with the
$space
parameter. (For backwards-compatibility, thisdoesn'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()
andcolor.invert()
now support the standard CSS algorithmfor 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 likehsl
andoklch
,this parameter also allows you to specify how hue interpolation is handled.
color.complement()
now supports a$space
parameter that indicates whichcolor space should be used to take the complement.
color.grayscale()
now operates in theoklch
space for non-legacy colors.color.ie-hex-str()
now automatically converts its color to thergb
spaceand 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()
, andcolor.blackness()
functions, as well as their global counterparts, shouldbe replaced with calls to
color.channel()
.The global
adjust-hue()
,saturate()
,desaturate()
,lighten()
,darken()
,transaprentize()
,fade-out()
,opacify()
, andfade-in()
functions should be replaced by
color.adjust()
orcolor.scale()
.Add a
global-builtin
future deprecation, which can be opted-into with the--future-deprecation
flag or thefutureDeprecations
option in the JS orDart API. This emits warnings when any global built-in functions that are
now available in
sass:
modules are called. It will become active by defaultin an upcoming release alongside the
@import
deprecation.Dart API
Added a
ColorSpace
class which represents the various color spaces definedin the CSS spec.
Added
SassColor.space
which returns a color's color space.Added
SassColor.channels
and.channelsOrNull
which returns a listof 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 thecorresponding 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 ofSassColor.channel()
.Deprecated
SassColor.changeRgb()
,.changeHsl()
, and.changeHwb()
infavor of
SassColor.changeChannels()
.Added
SassNumber.convertValueToUnit()
as a shorthand forSassNumber.convertValue()
with a single numerator.Added
InterpolationMethod
andHueInterpolationMethod
which collectivelyrepresent 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
insilenceDeprecations
when usingthe legacy API.
Modify
SassColor
to accept a newspace
option, with support for all thenew 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 channelvalues, 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 thecorresponding names.
Deprecate
SassColor.red
,.green
,.blue
,.hue
,.saturation
,.lightness
,.whiteness
, and.blackness
in favor ofSassColor.channel()
.Embedded Sass
Add
Color
SassScript value, with support for all the new color spacesdefined in Color Level 4.
Remove
RgbColor
,HslColor
andHwbColor
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 accessingSTATE_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
Component
interface get proper intellisensesveltejs/svelte-eslint-parser (svelte-eslint-parser)
v0.41.1
Compare Source
Patch Changes
8350bb5
Thanks @ota-meshi! - fix: incorrect runes inference when having empty compiler optionstypescript-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:
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
userEvent.upload
in playwright provider - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6442 (cf148)--inspect
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6433 (0499a)--inspect-brk
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6434 (7ab0f)--exclude-after-remap
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6309 (5932a){ spy: true }
instead of a factory - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6289 (95f02)vi.advanceTimersToNextFrame
- by @bnjm and @sheremet-va in https://github.com/vitest-dev/vitest/issues/6347 (8ff63)🐞 Bug Fixes
index
file - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6266 (081cf)expect.getState().testPath
always returns correct path - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6472 [(ac698)](https://redirect.github.com/vitest-dev/vitest/commit/ac698bConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.