-
Notifications
You must be signed in to change notification settings - Fork 71
chore(deps): update dependency sass to v1.94.0 #395
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
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ree6-backend ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
3fcb005 to
138bcf2
Compare
138bcf2 to
90edad2
Compare
90edad2 to
372a0e5
Compare
372a0e5 to
3660cd2
Compare
3660cd2 to
a82b767
Compare
a82b767 to
61d2bc5
Compare
61d2bc5 to
0ad9123
Compare
0ad9123 to
107b138
Compare
107b138 to
a9f7cf4
Compare
a9f7cf4 to
fc6f4ba
Compare
fc6f4ba to
82efd23
Compare
6b7c307 to
9c3be7e
Compare
9c3be7e to
9f3262f
Compare
f7ab52b to
32efaa8
Compare
|
32efaa8 to
5270ecb
Compare
5270ecb to
87516e0
Compare
87516e0 to
3781c91
Compare
3781c91 to
04762eb
Compare
0bffb3d to
591016b
Compare
591016b to
faa0236
Compare
faa0236 to
04667f4
Compare
|
04667f4 to
8e3a98e
Compare
8e3a98e to
6c4824e
Compare
|



This PR contains the following updates:
1.83.4->1.94.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
sass/dart-sass (sass)
v1.94.0Compare Source
Potentially breaking compatibility fix:
@functionrules whose namesbegin with
--are now parsed as unknown at-rules to support the plain CSS@functionrule. Within this rule, theresultproperty is parsed as rawCSS just like custom properties.
Potentially breaking compatibility fix:
@mixinrules whose names beginwith
--are now errors. These are not yet parsed as unknown at-rules becauseno browser currently supports CSS mixins.
v1.93.3Compare Source
v1.93.2Compare Source
JavaScript API
@sass/types.v1.93.1Compare Source
JavaScript API
@sass/types.v1.93.0Compare Source
@import, and the loaded file@uses a user-defined module as well as@includes a top-level mixin whichemits top-level declarations.
JavaScript API
@sass/typespackage which contains the type annotations used byboth the
sassandsass-embeddedpackage without any additional code ordependencies.
v1.92.1Compare Source
would not be passed as implicit configuration to a later imported, forwarded
module.
v1.92.0Compare Source
Breaking change: Emit declarations, childless at-rules, and comments in
the order they appear in the source even when they're interleaved with nested
rules. This obsoletes the
mixed-declsdeprecation.Breaking change: The function name
type()is now fully reserved for theplain CSS function. This means that
@functiondefinitions with the nametypewill produce errors, while function calls will be parsed as specialfunction strings.
Configuring private variables using
@use ... with,@forward ... with, andmeta.load-css(..., $with: ...)is now deprecated. Private variables werealways intended to be fully encapsulated within the module that defines them,
and this helps enforce that encapsulation.
Fix a bug where
@extendrules loaded through a mixture of@importand@userules could fail to apply correctly.Command-Line Interface
--watchmode, delete the source map when the associated source file isdeleted.
v1.91.0Compare Source
Potentially breaking change:
meta.inspect()(as well as other systemsthat use it such as
@debugand certain error messages) now emits numberswith as high precision as is available instead of rounding to the nearest
1e⁻¹⁰ as we do when serializing to CSS. This better fits the purpose of
meta.inspect(), which is to provide full information about the structure ofa Sass value.
Passing a rest argument (
$arg...) before a positional or named argument whencalling a function or mixin is now deprecated. This was always outside the
specified syntax, but it was historically treated the same as passing the rest
argument at the end of the argument list whether or not that matched the
visual order of the arguments.
v1.90.0Compare Source
@forwarded module to be loaded with a configuration when that modulehas already been loaded with a different configuration and the module
doesn't define any variables that would have been configured anyway.
v1.89.2Compare Source
Embedded Host
bufdependency.v1.89.1Compare Source
v1.89.0Compare Source
potential resolutions, as long as those resolutions all point to the same
file.
v1.88.0Compare Source
Allow custom properties with empty values (such as
--var:;).Fix a bug when calculating source spans for interpolations.
Dart and JS APIs
mixin object from one compilation to another.
Dart API
compileString()and related functions.v1.87.0Compare Source
nesting selector
&is loaded into a nested Sass context viameta.load-css()or@import, Sass now emits plain CSS nesting rather thanincorrectly combining it with the parent selector using a descendant
combinator.
v1.86.3Compare Source
a
..segment.v1.86.2Compare Source
v1.86.1Compare Source
file:URL case canonicalization on Windows andMac OS.
v1.86.0Compare Source
Add support for
%as an expression in its own right. It will still be parsedas the modulo operator when between two other expressions, but in any other
context it will be an expression whose value is the unquoted string
%.Consider
attr()to be a special number function that can be used as achannel in color functions.
Deprecate user-defined functions named
type()so that we can eventuallysupport the new CSS
type()function.Dart API
v1.85.1Compare Source
functions could incorrectly be treated as CSS math functions even though they
used Sass-only features, causing compilation failures. For example,
round(-$var / 2)previously threw an error but now works as intended.v1.85.0Compare Source
@extend. This causedunacceptable performance issues for certain heavy users of
@extend. We'lltry to find a more performant way to accomplish it in the future.
v1.84.0Compare Source
Allow newlines in whitespace in the indented syntax.
Potentially breaking bug fix: Selectors with unmatched brackets now always
produce a parser error. Previously, some edge cases like
[foo#{"]:is(bar"}) {a: b}would compile without error, but this was an unintentional bug.Fix a bug in which various Color Level 4 functions weren't allowed in plain
CSS.
Fix the error message for
@extendwithout a selector and possibly otherparsing edge-cases in contexts that allow interpolation.
Embedded Host
SassBooleantype to adhere to the spec,now using a class instead of an interface.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.