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:
7.25.2
->7.25.7
7.25.4
->7.25.7
29.5.12
->29.5.13
20.16.5
->20.16.11
8.5.0
->8.8.1
8.5.0
->8.8.1
0.23.1
->0.24.0
9.1.5
->9.1.6
3.1.4
->3.1.7
6.2.2
->6.2.3
8.4.45
->8.4.47
8.1.0
->8.2.0
1.78.0
->1.79.4
Release Notes
babel/babel (@babel/core)
v7.25.7
Compare Source
🐛 Bug Fix
babel-helper-validator-identifier
babel-traverse
babel-plugin-transform-classes
super()
check (@nicolo-ribaudo)babel-generator
infer
in compact mode (@nicolo-ribaudo)[no LineTerminator here]
after nodes (@nicolo-ribaudo)💅 Polish
babel-types
🏠 Internal
babel-core
--experimental-require-module
(@nicolo-ribaudo)babel-helper-compilation-targets
,babel-helper-plugin-utils
,babel-preset-env
babel-plugin-proposal-destructuring-private
,babel-plugin-syntax-decimal
,babel-plugin-syntax-import-reflection
,babel-standalone
babel-generator
[no LineTerminator here]
before nodes (@nicolo-ribaudo)🏃♀️ Performance
babel-plugin-transform-typescript
babel-types
BABEL_TYPES_8_BREAKING
at startup (@nicolo-ribaudo)typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.8.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.8.0
Compare Source
🚀 Features
eslint-plugin: [no-unnecessary-condition] add checkTypePredicates
eslint-plugin: [return-await] check for-await loop iteree
🩹 Fixes
remove
export type *
in d.ts to support TS<5.0eslint-plugin: [no-unnecessary-template-expression] should underline template syntax with squiggly lines
type-utils: check for type parameters on
isBuiltinSymbolLikeRecurser()
eslint-plugin: [no-deprecated] max callstack exceeded when class implements itself
eslint-plugin: [no-misused-promises] check contextual type
eslint-plugin: [prefer-literal-enum-member] allow nested bitwise operations
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.7.0
Compare Source
🚀 Features
eslint-plugin: [no-unsafe-call] check calls of Function
eslint-plugin: [consistent-type-exports] check
export *
exports to see if all exported members are types🩹 Fixes
eslint-plugin: properly coerce all types to string in
getStaticMemberAccessValue
eslint-plugin: [no-deprecated] report on imported deprecated variables
eslint-plugin: [no-confusing-non-null-assertion] check !in and !instanceof
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.6.0
Compare Source
🚀 Features
add
allow
option forrestrict-template-expressions
type-utils: isNullableType add Void logic
eslint-plugin: [no-unnecessary-condition] check switch cases
eslint-plugin: [no-misused-promises] check array predicate return
🩹 Fixes
eslint-plugin: [no-deprecated] don't report recursive types in destructuring assignment twice
eslint-plugin: [no-deprecated] report on deprecated variables used in destructuring assignment
eslint-plugin: [no-deprecated] report on deprecated properties with function-like types
eslint-plugin: [no-unnecessary-condition] properly reflect multiple negations in message
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.8.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.8.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.7.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.6.0
Compare Source
evanw/esbuild (esbuild)
v0.24.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.23.0
or~0.23.0
. See npm's documentation about semver for more information.Drop support for older platforms (#3902)
This release drops support for the following operating system:
This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.
Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
Fix class field decorators in TypeScript if
useDefineForClassFields
isfalse
(#3913)Setting the
useDefineForClassFields
flag tofalse
intsconfig.json
means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.Avoid incorrect cycle warning with
tsconfig.json
multiple inheritance (#3898)TypeScript 5.0 introduced multiple inheritance for
tsconfig.json
files whereextends
can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release,tsconfig.json
files containing this edge case should work correctly without generating a warning.Handle Yarn Plug'n'Play stack overflow with
tsconfig.json
(#3915)Previously a
tsconfig.json
file thatextends
another file in a package with anexports
map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around more issues with Deno 1.31+ (#3917)
This version of Deno broke the
stdin
andstdout
properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. whenimport.meta.main
istrue
). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.This fix was contributed by @Joshix-1.
typicode/husky (husky)
v9.1.6
Compare Source
remy/nodemon (nodemon)
v3.1.7
Compare Source
v3.1.6
Compare Source
Bug Fixes
v3.1.5
Compare Source
bcomnes/npm-run-all2 (npm-run-all2)
v6.2.3
Compare Source
Commits
c43fa2b
dc2d7da
postcss/postcss (postcss)
v8.4.47
Compare Source
v8.4.46
Compare Source
Cannot read properties of undefined (reading 'before')
.adamreisnz/replace-in-file (replace-in-file)
v8.2.0
Compare Source
sass/dart-sass (sass)
v1.79.4
Compare Source
JS API
green
orblue
tocolor.change()
for legacycolors would fail.
v1.79.3
Compare Source
$channel
parameter in the suggested replacement forcolor.red()
,color.green()
,color.blue()
,color.hue()
,color.saturation()
,color.lightness()
,color.whiteness()
, andcolor.blackness()
to use a quoted string.v1.79.2
Compare Source
Add a
$space
parameter to the suggested replacement forcolor.red()
,color.green()
,color.blue()
,color.hue()
,color.saturation()
,color.lightness()
,color.whiteness()
, andcolor.blackness()
.Update deprecation warnings for the legacy JS API to include a link to
relevant documentation.
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.Configuration
📅 Schedule: Branch creation - "after 9am and before 5pm 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.