chore(deps): bump sass from 1.72.0 to ^1.79.5 (main) #10257
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:
^1.72.0
->^1.79.5
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
sass/dart-sass (sass)
v1.79.5
Compare Source
Changes to how
selector.unify()
and@extend
combine selectors:The relative order of pseudo-classes (like
:hover
) and pseudo-elements(like
::before
) within each original selector is now preserved whenthey're combined.
Pseudo selectors are now consistently placed at the end of the combined
selector, regardless of which selector they came from. Previously, this
reordering only applied to pseudo-selectors in the second selector.
Tweak the color transformation matrices for OKLab and OKLCH to match the
newer, more accurate values in the CSS spec.
Fix a slight inaccuracy case when converting to
srgb-linear
anddisplay-p3
.Potentially breaking bug fix:
math.unit()
now wraps multiple denominatorunits in parentheses. For example,
px/(em*em)
instead ofpx/em*em
.Command-Line Interface
@parcel/watcher
to watch the filesystem when running from JavaScript andnot using
--poll
. This should mitigate more frequent failures users havebeen seeing since version 4.0.0 of Chokidar, our previous watching tool, was
released.
JS API
SassColor.interpolate()
to allow an undefinedoptions
parameter, asthe types indicate.
Embedded 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.v1.78.0
Compare Source
The
meta.feature-exists
function is now deprecated. This deprecation isnamed
feature-exists
.Fix a crash when using
@at-root
without any queries or children in theindented syntax.
JS API
Backport the deprecation options (
fatalDeprecations
,futureDeprecations
,and
silenceDeprecations
) to the legacy JS API. The legacy JS API is itselfdeprecated, and you should move off of it if possible, but this will allow
users of bundlers and other tools that are still using the legacy API to
still control deprecation warnings.
Fix a bug where accessing
SourceSpan.url
would crash when a relative URL waspassed to the Sass API.
Embedded Sass
Explicitly expose a
sass
executable from thesass-embedded
npm package.This was intended to be included in 1.63.0, but due to the way
platform-specific dependency executables are installed it did not work as
intended. Now users can run
npx sass
for local installs or justsass
whensass-embedded
is installed globally.Add linux-riscv64, linux-musl-riscv64, and android-riscv64 support for the
sass-embedded
npm package.Fix an edge case where the Dart VM could hang when shutting down when requests
were in flight.
Fix a race condition where the embedded host could fail to shut down if it was
closed around the same time a new compilation was started.
Fix a bug where parse-time deprecation warnings could not be controlled by
the deprecation options in some circumstances.
v1.77.8
Compare Source
v1.77.7
Compare Source
Declarations that appear after nested rules are deprecated, because the
semantics Sass has historically used are different from the semantics
specified by CSS. In the future, Sass will adopt the standard CSS semantics.
See the Sass website for details.
Potentially breaking bug fix:
//
in certain places such as unknownat-rule values was being preserved in the CSS output, leading to potentially
invalid CSS. It's now properly parsed as a silent comment and omitted from the
CSS output.
v1.77.6
Compare Source
between the end of Sass statements and the following semicolon.
v1.77.5
Compare Source
@extend
.v1.77.4
Compare Source
Embedded Sass
Support passing
Version
input forfatalDeprecations
as string overembedded protocol.
Fix a bug in the JS Embedded Host where
Version
could be incorrectly acceptedas input for
silenceDeprecations
andfutureDeprecations
in pure JS.v1.77.3
Compare Source
Dart API
Deprecation.duplicateVariableFlags
has been deprecated and replaced withDeprecation.duplicateVarFlags
to make it consistent with theduplicate-var-flags
name used on the command line and in the JS API.v1.77.2
Compare Source
Don't emit deprecation warnings for functions and mixins beginning with
__
.Allow user-defined functions whose names begin with
_
and otherwise looklike vendor-prefixed functions with special CSS syntax.
Command-Line Interface
Properly handle the
--silence-deprecation
flag.Handle the
--fatal-deprecation
and--future-deprecation
flags for--interactive
mode.v1.77.1
Compare Source
v1.77.0
Compare Source
v1.76.0
Compare Source
Throw errors for misplaced statements in keyframe blocks.
Mixins and functions whose names begin with
--
are now deprecated forforwards-compatibility with the in-progress CSS functions and mixins spec.
This deprecation is named
css-function-mixin
.v1.75.0
Compare Source
when custom importers or the Node.js package importer made decisions based on
the URL of the containing stylesheet.
JS API
importer
to be passed withouturl
inStringOptionsWithImporter
.v1.74.1
Compare Source
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.