-
Notifications
You must be signed in to change notification settings - Fork 5
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 dependency sass to v1.69.5 #1397
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/sass-1.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sunya9/beta/29yjcMLPSr8FEfuN9db2SjuvV5qa |
✨✨ That's perfect, there is no visual difference! ✨✨ Check out the report here. |
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 14, 2021 01:02
a823a5c
to
09ae891
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.39.2
chore(deps): update dependency sass to v1.40.0
Sep 14, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 14, 2021 10:14
09ae891
to
9baa257
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.40.0
chore(deps): update dependency sass to v1.40.1
Sep 14, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 15, 2021 01:32
9baa257
to
351b7b0
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.40.1
chore(deps): update dependency sass to v1.41.0
Sep 15, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 16, 2021 23:14
351b7b0
to
66aac10
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.41.0
chore(deps): update dependency sass to v1.41.1
Sep 16, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 21, 2021 01:04
66aac10
to
bc30929
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.41.1
chore(deps): update dependency sass to v1.42.0
Sep 21, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 22, 2021 08:15
bc30929
to
2614b6d
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.42.0
chore(deps): update dependency sass to v1.42.1
Sep 22, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 13, 2021 23:06
2614b6d
to
6c2c778
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.42.1
chore(deps): update dependency sass to v1.43.2
Oct 13, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 21, 2021 21:16
6c2c778
to
a0baac3
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.43.2
chore(deps): update dependency sass to v1.43.3
Oct 21, 2021
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 26, 2021 22:18
a0baac3
to
179a488
Compare
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
August 17, 2023 20:14
af8e5a8
to
2e6cdd9
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.66.0
chore(deps): update dependency sass to v1.66.1
Aug 18, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
August 18, 2023 23:23
2e6cdd9
to
ccc4054
Compare
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 14, 2023 01:08
ccc4054
to
70711be
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.66.1
chore(deps): update dependency sass to v1.67.0
Sep 14, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
September 21, 2023 03:54
70711be
to
0be8049
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.67.0
chore(deps): update dependency sass to v1.68.0
Sep 21, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 6, 2023 00:12
0be8049
to
f69e183
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.68.0
chore(deps): update dependency sass to v1.69.0
Oct 6, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 10, 2023 00:53
f69e183
to
394d95f
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.69.0
chore(deps): update dependency sass to v1.69.1
Oct 10, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 10, 2023 19:36
394d95f
to
1302656
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.69.1
chore(deps): update dependency sass to v1.69.2
Oct 10, 2023
renovate
bot
changed the title
chore(deps): update dependency sass to v1.69.2
chore(deps): update dependency sass to v1.69.3
Oct 12, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 12, 2023 00:29
1302656
to
9d57a63
Compare
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 18, 2023 02:02
9d57a63
to
5e9adc7
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.69.3
chore(deps): update dependency sass to v1.69.4
Oct 18, 2023
renovate
bot
force-pushed
the
renovate/sass-1.x
branch
from
October 26, 2023 01:45
5e9adc7
to
408a44d
Compare
renovate
bot
changed the title
chore(deps): update dependency sass to v1.69.4
chore(deps): update dependency sass to v1.69.5
Oct 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.39.0
->1.69.5
Release Notes
sass/dart-sass (sass)
v1.69.5
Compare Source
JS API
v1.69.4
Compare Source
v1.69.3
Compare Source
Embedded Sass
package.json
.v1.69.2
Compare Source
JS API
variable named
process
.v1.69.1
Compare Source
v1.69.0
Compare Source
Add a
meta.get-mixin()
function that returns a mixin as a first-class Sassvalue.
Add a
meta.apply()
mixin that includes a mixin value.Add a
meta.module-mixins()
function which returns a map from mixin names ina module to the first-class mixins that belong to those names.
Add a
meta.accepts-content()
function which returns whether or not a mixinvalue can take a content block.
Add support for the relative color syntax from CSS Color 5. This syntax
cannot be used to create Sass color values. It is always emitted as-is in the
CSS output.
Dart API
Deprecation.calcInterp
since it was never actually emitted as adeprecation.
Embedded Sass
protocol error was immediately followed by another request.
v1.68.0
Compare Source
abs-percent
deprecation.JS API
Non-filesystem importers can now set the
nonCanonicalScheme
field, whichdeclares that one or more URL schemes (without
:
) will never be used forURLs returned by the
canonicalize()
method.Add a
containingUrl
field to thecanonicalize()
andfindFileUrl()
methods of importers, which is set to the canonical URL of the stylesheet that
contains the current load. For filesystem importers, this is always set; for
other importers, it's set only if the current load has no URL scheme, or if
its URL scheme is declared as non-canonical by the importer.
Dart API
Add
AsyncImporter.isNonCanonicalScheme
, which importers (async or sync) canuse to indicate that a certain URL scheme will never be used for URLs returned
by the
canonicalize()
method.Add
AsyncImporter.containingUrl
, which is set during calls to thecanonicalize()
method to the canonical URL of the stylesheet that containsthe current load. This is set only if the current load has no URL scheme, or
if its URL scheme is declared as non-canonical by the importer.
Embedded Sass
The
CalculationValue.interpolation
field is deprecated and will be removedin a future version. It will no longer be set by the compiler, and if the host
sets it it will be treated as equivalent to
CalculationValue.string
exceptthat
"("
and")"
will be added to the beginning and end of the stringvalues.
Properly include TypeScript types in the
sass-embedded
package.v1.67.0
Compare Source
All functions defined in CSS Values and Units 4 are now once again parsed as
calculation objects:
round()
,mod()
,rem()
,sin()
,cos()
,tan()
,asin()
,acos()
,atan()
,atan2()
,pow()
,sqrt()
,hypot()
,log()
,exp()
,abs()
, andsign()
.Unlike in 1.65.0, function calls are not locked into being parsed as
calculations or plain Sass functions at parse-time. This means that
user-defined functions will take precedence over CSS calculations of the same
name. Although the function names
calc()
andclamp()
are still forbidden,users may continue to freely define functions whose names overlap with other
CSS calculations (including
abs()
,min()
,max()
, andround()
whosenames overlap with global Sass functions).
Breaking change: As a consequence of the change in calculation parsing
described above, calculation functions containing interpolation are now parsed
more strictly than before. However, almost all interpolations that would
have produced valid CSS will continue to work. The only exception is
#{$variable}%
which is not valid in Sass and is no longer valid incalculations. Instead of this, either use
$variable
directly and ensure italready has the
%
unit, or write($variable * 1%)
.Potentially breaking bug fix: The importer used to load a given file is no
longer used to load absolute URLs that appear in that file. This was
unintented behavior that contradicted the Sass specification. Absolute URLs
will now correctly be loaded only from the global importer list. This applies
to the modern JS API, the Dart API, and the embedded protocol.
Embedded Sass
files or files that require many importer or function call round-trips with
the embedded host.
v1.66.1
Compare Source
JS API
callback that threw a string, boolean, number, symbol, or bignum.
v1.66.0
Compare Source
Breaking change: Drop support for the additional CSS calculations defined
in CSS Values and Units 4. Custom Sass functions whose names overlapped with
these new CSS functions were being parsed as CSS calculations instead, causing
an unintentional breaking change outside our normal [compatibility policy] for
CSS compatibility changes.
Support will be added again in a future version, but only after Sass has
emitted a deprecation warning for all functions that will break for at least
three months prior to the breakage.
v1.65.1
Compare Source
1.65.0
.v1.65.0
Compare Source
All functions defined in CSS Values and Units 4 are now parsed as calculation
objects:
round()
,mod()
,rem()
,sin()
,cos()
,tan()
,asin()
,acos()
,atan()
,atan2()
,pow()
,sqrt()
,hypot()
,log()
,exp()
,abs()
, andsign()
.Deprecate explicitly passing the
%
unit to the globalabs()
function. Infuture releases, this will emit a CSS abs() function to be resolved by the
browser. This deprecation is named
abs-percent
.v1.64.2
Compare Source
v1.64.1
Compare Source
Embedded Sass
SassCalculation.clamp()
with less than 3 argumentswould throw an error.
v1.64.0
Compare Source
Comments that appear before or between
@use
and@forward
rules are nowemitted in source order as much as possible, instead of always being emitted
after the CSS of all module dependencies.
Fix a bug where an interpolation in a custom property name crashed if the file
was loaded by a
@use
nested in an@import
.JavaScript API
Add a new
SassCalculation
type that represents the calculation objects addedin Dart Sass 1.40.0.
Add
Value.assertCalculation()
, which returns the value if it's aSassCalculation
and throws an error otherwise.Produce a better error message when an environment that supports some Node.js
APIs loads the browser entrypoint but attempts to access the filesystem.
Embedded Sass
@imports
failed to load when using thedeprecated functions
render
orrenderSync
and those relative imports wereloaded multiple times across different files.
v1.63.6
Compare Source
JavaScript API
import sass from 'sass'
again after it was broken in the last release.Embedded Sass
exports
declaration inpackage.json
.v1.63.5
Compare Source
JavaScript API
require()
and ESMimport
could crash on Node.js.Embedded Sass
Fix a deadlock when running at high concurrency on 32-bit systems.
Fix a race condition where the embedded compiler could deadlock or crash if a
compilation ID was reused immediately after the compilation completed.
v1.63.4
Compare Source
JavaScript API
Re-enable support for
import sass from 'sass'
when loading the package froman ESM module in Node.js. However, this syntax is now deprecated; ESM users
should use
import * as sass from 'sass'
instead.On the browser and other ESM-only platforms, only
import * as sass from 'sass'
is supported.Properly export the legacy API values
TRUE
,FALSE
,NULL
, andtypes
fromthe ECMAScript module API.
Embedded Sass
Fix a race condition where closing standard input while requests are in-flight
could sometimes cause the process to hang rather than shutting down
gracefully.
Properly include the root stylesheet's URL in the set of loaded URLs when it
fails to parse.
v1.63.3
Compare Source
JavaScript API
v1.63.2
Compare Source
v1.63.1
Compare Source
v1.63.0
Compare Source
JavaScript API
instructions for use are in the README.
Embedded Sass
The Dart Sass embedded compiler is now included as part of the primary Dart
Sass distribution, rather than a separate executable. To use the embedded
compiler, just run
sass --embedded
from any Sass executable (other than thepure JS executable).
The Node.js embedded host will still be distributed as the
sass-embedded
package on npm. The only change is that it will now provide direct access to a
sass
executable with the same CLI as thesass
package.The Dart Sass embedded compiler now uses version 2.0.0 of the Sass embedded
protocol. See the spec for a full description of the
protocol, and the changelog for a summary of
changes since version 1.2.0.
The Dart Sass embedded compiler now runs multiple simultaneous compilations in
parallel, rather than serially.
v1.62.1
Compare Source
:has(+ &)
and related constructs would drop the leadingcombinator.
v1.62.0
Compare Source
Deprecate the use of multiple
!global
or!default
flags on the samevariable. This deprecation is named
duplicate-var-flags
.Allow special numbers like
var()
orcalc()
in the global functions:grayscale()
,invert()
,saturate()
, andopacity()
. These are alsonative CSS
filter
functions. This is in addition to number values which werealready allowed.
Fix a cosmetic bug where an outer rule could be duplicated after nesting was
resolved, instead of re-using a shared rule.
v1.61.0
Compare Source
Potentially breaking change: Drop support for End-of-Life Node.js 12.
Fix remaining cases for the performance regression introduced in 1.59.0.
Embedded Sass
legacy API.
v1.60.0
Compare Source
Add support for the
pi
,e
,infinity
,-infinity
, andNaN
constants incalculations. These will be interpreted as the corresponding numbers.
Add support for unknown constants in calculations. These will be interpreted
as unquoted strings.
Serialize numbers with value
infinity
,-infinity
, andNaN
tocalc()
expressions rather than CSS-invalid identifiers. Numbers with complex units
still can't be serialized.
v1.59.3
Compare Source
Fix a performance regression introduced in 1.59.0.
The NPM release of 1.59.0 dropped support for Node 12 without actually
indicating so in its pubspec. This release temporarily adds back support so
that the latest Sass version that declares it supports Node 12 actually does
so. However, Node 12 is now end-of-life, so we will drop support for it
properly in an upcoming release.
v1.59.2
Compare Source
v1.59.1
Compare Source
v1.59.0
Compare Source
Command Line Interface
Added a new
--fatal-deprecation
flag that lets you treat a deprecationwarning as an error. You can pass an individual deprecation ID
(e.g.
slash-div
) or you can pass a Dart Sass version to treat alldeprecations initially emitted in that version or earlier as errors.
New
--future-deprecation
flag that lets you opt into warning for use ofcertain features that will be deprecated in the future. At the moment, the
only option is
--future-deprecation=import
, which will emit warnings forSass
@import
rules, which are not yet deprecated, but will be in the future.Dart API
New
Deprecation
enum, which contains the different current and futuredeprecations used by the new CLI flags.
The
compile
methods now take infatalDeprecations
andfutureDeprecations
parameters, which work similarly to the CLI flags.
v1.58.3
Compare Source
v1.58.2
Compare Source
Command Line Interface
Add a timestamp to messages printed in
--watch
mode.Print better
calc()
-based suggestions for/
-as-division expression thatcontain calculation-incompatible constructs like unary minus.
v1.58.1
Compare Source
hsl()
colors. Thedeg
unit isincompatible with IE, and while that officially falls outside our
compatibility policy, it's better to lean towards greater compatibility.
v1.58.0
Compare Source
Remove sourcemap comments from Sass sources. The generated sourcemap comment
for the compiled CSS output remains unaffected.
Fix a bug in
@extend
logic where certain selectors with three or morecombinators were incorrectly considered superselectors of similar selectors
with fewer combinators, causing them to be incorrectly trimmed from the
output.
Produce a better error message for a number with a leading
+
or-
, adecimal point, but no digits.
Produce a better error message for a nested property whose name starts with
--
.Fix a crash when a selector ends in an escaped backslash.
Add the relative length units from CSS Values 4 and CSS Contain 3 as known
units to validate bad computation in
calc
.Command Line Interface
--watch
flag will now track loads through calls tometa.load-css()
aslong as their URLs are literal strings without any interpolation.
v1.57.1
Compare Source
v1.57.0
Compare Source
split($string, $separator, $limit: null)
function tosass:string
that splits a string into separate substrings based on a separator string.
JavaScript API
Potentially breaking bug fix: Custom functions in both the modern and
legacy API now properly reject signatures with whitespace between the function
name and parentheses.
Custom functions in the legacy API now allow signatures with whitespace before
the function name, to match a bug in Node Sass.
Dart API
Callable.fromSignature()
andAsyncCallable.fromSignature()
now reject signatures with whitespace betweenthe function name and parentheses.
v1.56.2
Compare Source
Embedded Sass
protocol.
v1.56.1
Compare Source
Embedded Sass
contents
is actually a string and whethersourceMapUrl
is an absolute URL.v1.56.0
Compare Source
Potentially breaking change: To match the CSS spec, SassScript expressions
beginning with
not
or(
are no longer supported at the beginning ofparenthesized sections of media queries. For example,
@​media (width >= 500px) and (not (grid))
will now be emitted unchanged, instead of producing
@​media (width >= 500px) and (false)
See the Sass website for details.
Potentially breaking bug fix: Angle units like
rad
orturn
are nowproperly converted to equivalent
deg
values forhsl()
,hsla()
,adjust-hue()
,color.adjust()
, andcolor.change()
.See the Sass website for
details.
Fix indentation for selectors that span multiple lines in a
@media
query.Emit a deprecation warning when passing
$alpha
values with units tocolor.adjust()
orcolor.change()
. This will be an error in Dart Sass2.0.0.
See the Sass website for
details.
Emit a deprecation warning when passing a
$weight
value with no units orwith units other than
%
tocolor.mix()
. This will be an error in Dart Sass2.0.0.
See the Sass website for
details.
Emit a deprecation warning when passing
$n
values with units tolist.nth()
or
list.set-nth()
. This will be an error in Dart Sass 2.0.0.See the Sass website for
details.
Improve existing deprecation warnings to wrap
/
-as-division suggestions incalc()
expressions.Properly mark the warning for passing numbers with units to
random()
as adeprecation warning.
Fix a bug where
@extend
could behave unpredicatably when used along withmeta.load-css()
and shared modules that contained no CSS themselves butloaded CSS from other modules.
Dart API
sassIndex
with units toValue.sassIndexToListIndex()
. This will be an error in Dart Sass 2.0.0.JS API
Importer results now validate whether
contents
is actually a string type.Importer result argument errors are now rendered correctly.
v1.55.0
Compare Source
Potentially breaking bug fix: Sass numbers are now universally stored as
64-bit floating-point numbers, rather than sometimes being stored as integers.
This will generally make arithmetic with very large numbers more reliable and
more consistent across platforms, but it does mean that numbers between nine
quadrillion and nine quintillion will no longer be represented with full
accuracy when compiling Sass on the Dart VM.
Potentially breaking bug fix: Sass equality is now properly transitive.
Two numbers are now considered equal (after doing unit conversions) if they
round to the same
1e-11
th. Previously, numbers were considered equal if theywere within
1e-11
of one another, which led to some circumstances where$a == $b
and$b == $c
but$a != $b
.Potentially breaking bug fix: Various functions in
sass:math
no longertreat floating-point numbers that are very close (but not identical) to
integers as integers. Instead, these functions now follow the floating-point
specification exactly. For example,
math.pow(0.000000000001, -1)
now returns1000000000000
instead ofInfinity
.Emit a deprecation warning for
$a -$b
and$a +$b
, since these look likethey could be unary operations but they're actually parsed as binary
operations. Either explicitly write
$a - $b
or$a (-$b)
. Seehttps://sass-lang.com/d/strict-unary for more details.
Dart API
Add an optional
argumentName
parameter toSassScriptException()
to make iteasier to throw exceptions associated with particular argument names.
Most APIs that previously returned
num
now returndouble
. All APIscontinue to accept
num
, although in Dart 2.0.0 these APIs will be changedto accept only
double
.JS API
accessible by the JS API.
v1.54.9
Compare Source
@media
query deprecation warnings.v1.54.8
Compare Source
v1.54.7
Compare Source
v1.54.6
Compare Source
@media
query could be incorrectly omitted from astylesheet if it had multiple levels of nested
@media
queries within itand the inner queries were mergeable but the outer query was not.
v1.54.5
Compare Source
Properly consider
a ~ c
to be a superselector ofa ~ b ~ c
anda + b + c
.Properly consider
b > c
to be a superselector ofa > b > c
, and similarlyfor other combinators.
Properly calculate specificity for selector pseudoclasses.
Deprecate use of
random()
when$limit
has units to make it explicit thatrandom()
currently ignores units. A future version will no longer ignoreunits.
Don't throw an error when the same module is
@forward
ed multiple timesthrough a configured module.
Embedded Sass
install, the
sass-embedded
npm package now declares optional dependencies onplatform-specific embedded compiler packages.
v1.54.4
Compare Source
out-of-bounds to various color functions.
v1.54.3
Compare Source
v1.54.2
Compare Source
v1.54.1
Compare Source
@extend
andselector.unify()
, ensure that:root
,:scope
,:host
, and:host-context
only appear at the beginningof complex selectors.
v1.54.0
Compare Source
Deprecate selectors with leading or trailing combinators, or with multiple
combinators in a row. If they're included in style rules after nesting is
resolved, Sass will now produce a deprecation warning and, in most cases, omit
the selector. Leading and trailing combinators can still be freely used for
nesting purposes.
See https://sass-lang.com/d/bogus-combinators for more details.
Add partial support for new media query syntax from Media Queries Level 4. The
only exception are logical operations nested within parentheses, as these were
previously interpreted differently as SassScript expressions.
A parenthesized media condition that begins with
not
or an openingparenthesis now produces a deprecation warning. In a future release, these
will be interpreted as plain CSS instead.
Deprecate passing non-
deg
units tocolor.hwb()
's$hue
argument.Fix a number of bugs when determining whether selectors with pseudo-elements
are superselectors.
Treat
*
as a superselector of all selectors.Dart API
fakeFromImport()
function for testing custom importersthat use
AsyncImporter.fromImport
.JS API
Add a
charset
option that controls whether or not Sass emits a@charset
/BOM for non-ASCII stylesheets.Fix Sass npm package types for TS 4.7+ Node16 and NodeNext module resolution.
v1.53.0
Compare Source
var()
with an empty second argument, such asvar(--side, )
.JS API
meta.load-css()
would sometimes resolve relative URLsincorrectly when called from a mixin using the legacy JS API.
Embedded Sass
v1.52.3
Compare Source
/* ... */
) appear twice in a rowacross two different imports which themselves imported the same file each.
v1.52.2
Compare Source
/* ... */
) instead of pushingthe comment to the next line.
v1.52.1
Compare Source
Command Line Interface
--watch
mode would close immediately in TTY mode. This wascaused by our change to close
--watch
when stdin was closed outside of TTYmode, which has been reverted for now while we work on a fix.
v1.52.0
Compare Source
Add support for arbitrary modifiers at the end of plain CSS imports, in
addition to the existing
supports()
and media queries. Sass now allows anysequence of identifiers of functions after the URL of an import for forwards
compatibility with future additions to the CSS spec.
Fix an issue where source locations tracked through variable references could
potentially become incorrect.
Fix a bug where a loud comment in the source can break the source map when
embedding the sources, when using the command-line interface or the legacy JS
API.
JS API
SassNumber.assertUnit()
andSassNumber.assertNoUnits()
now correctlyreturn the number called on when it passes the assertion.
v1.51.0
Compare Source
Potentially breaking change: Change the order of maps returned by
map.deep-merge()
to match those returned bymap.merge()
. All keys thatappeared in the first map will now be listed first in the same order they
appeared in that map, followed by any new keys added from the second map.
Improve the string output of some AST nodes in error messages.
v1.50.1
Compare Source
Embedded Sass
The JS embedded host and the embedded compiler will now properly avoid
resolving imports relative to the current working directory unless
'.'
ispassed as a load path.
Fix a bug in the JS embedded host's implementation of the legacy JS API where
imports that began with
/
could crash on Windows.v1.50.0
Compare Source
@extend
now treats [:where()
][:where()] the same as:is()
.Command Line Interface
--watch
command to stoprunning.
Embedded Sass
Fix a bug where the JS embedded host crashed when invoking a legacy importer
after resolving a relative filesystem import.
Improve error messages when returning non-
Object
values from legacyimporters.
v1.49.11
Compare Source
Embedded Sass
id
field for allOutboundMessage
s.v1.49.10
Compare Source
Quiet deps mode now silences compiler warnings in mixins and functions that
are defined in dependencies even if they're invoked from application
stylesheets.
In expanded mode, Sass will now emit colors using
rgb()
,rbga()
,hsl()
,and
hsla()
function notation if they were defined using the correspondingnotation. As per our browser support policy, this change was only done once
95% of browsers were confirmed to support this output format, and so is not
considered a breaking change.
Note that this output format is intended for human readability and not for
interoperability with other tools. As always, Sass targets the CSS
specification, and any tool that consumes Sass's output should parse all
colors that are supported by the CSS spec.
Fix a bug in which a color written using the four- or eight-digit hex format
could be emitted as a hex color rather than a format with higher browser
compatibility.
Calculations are no longer simplified within supports declarations
v1.49.9
Compare Source
Embedded Sass
list.
v1.49.8
Compare Source
JS API
Node 17.
Embedded Sass
importers to the legacy API.
v1.49.7
Compare Source
Embedded Sass
First stable release the
sass-embedded
npm package that contains the Node.jsEmbedded Host.
First stable release of the
sass_embedded
pub package that contains theEmbedded Dart Sass compiler.
v1.49.6
Compare Source
v1.49.5
Compare Source
v1.49.4
Compare Source
v1.49.3
Compare Source
v1.49.2
Compare Source
v1.49.1
Compare Source
Embedded Sass
id
field for allOutboundMessage
s.v1.49.0
Compare Source
string.insert
with certain negative indices.JS API
sourceMapIncludeSources
option in the new JS API.TypeScript Declarations
LegacyPluginThis.options.linefeed
was typed to returnabbreviations when it actually returned literal linefeed characters.
v1.48.0
Compare Source
JS API
setting
LegacyResult.map
toundefined
rather thannull
.TypeScript Declarations
NULL
constant.v1.47.0
Compare Source
JS API
TypeScript Declarations
TRUE
andFALSE
constants.v1.46.0
Compare Source
JS API
passing
undefined
rather thannull
toLogger.warn()
for an unsetspan
.TypeScript Declarations
Add a declaration for the
LegacyPluginThis.options.context
field.Update the definition of
LegacyAsyncFunction
to include explicit definitionswith zero through six arguments before the
done
parameter. This makes itpossible for TypeScript users to pass in callbacks that take a specific number
of arguments, rather than having to declare a callback that takes an arbitrary
number.
Add a declaration for
types.Error
, a legacy API class that can be returnedby asynchronous functions to signal asynchronous errors.
Add a
LegacyAsyncFunctionDone
type for thedone
callback that's passed toLegacyAsyncFunction
.v1.45.2
Compare Source
JS API
separator
parameter for
new SassArgumentList()
to','
rather thannull
. Thismatches the API specification.
v1.45.1
Compare Source
Potentially breaking bug fix: Properly parse custom properties in
@supports
conditions. Note that this means that SassScript expressions onthe right-hand side of custom property
@supports
queries now need to beinterpolated, as per https://sass-lang.com/d/css-vars.
Potentially breaking bug fix: Fix a bug where
inspect()
was notproperly printing nested, empty, bracketed lists.
v1.45.0
Compare Source
JS API
This release includes an entirely new JavaScript API, designed to be more
idiomatic, performant, and usable. The old API will continue to be supported
until Dart Sass 2.0.0, but it is now considered deprecated and should be avoided
for new code.
The new API includes:
compile()
andcompileAsync()
functions that take Sass file paths andreturn the result of compiling them to CSS. The async function returns a
Promise
rather than using a callback-based API.compileString()
andcompileStringAsync()
functions that take a string ofSass source and compiles it to CSS. As above, the async function returns a
Promise
.A new importer API that more closely matches the Sass specification's logic
for resolving loads. This makes it much easier for Sass to cache information
across
@import
and@use
rules, which substantially improves performancefor applications that rely heavily on repeated
@import
s.A new custom function API, including much more usable JS representations of
Sass value types complete with type-assertion functions, easy map and list
lookups, and compatibility with the [
immutable
][immutable] package. Unlike in thelegacy API, function callbacks now take one argument which contains an array
of Sass values (rather than taking a separate JS argument for each Sass
argument).
For full documentation of this API, please see the Sass website.
This release also adds TypeScript type definitions.
v1.44.0
Compare Source
calc()
as an alternative in/
-as-division deprecation messages.Dart API
Add
SassNumber.convert()
andSassNumber.convertValue()
. These work likeSassNumber.coerce()
andSassNumber.coerceValue()
, except they don't treatunitless numbers as universally compatible.
Fix a bug where
SassNumber.coerceToMatch()
andSassNumber.coerceValueToMatch()
wouldn't coerce single-unit numbers tomatch unitless numbers.
v1.43.5
Compare Source
Fix a bug where calculations with different operators were incorrectly
considered equal.
Properly parse attribute selectors with empty namespaces.
JS API
own debugging purposes.
v1.43.4
Compare Source
JS API
logger
option was ignored for therender()
function.v1.43.3
Compare Source
v1.43.2
Compare Source
@use
rule is nota valid identifier.
v1.42.1
Compare Source
being resolved correctly if there was a parenthesized interpolation elsewhere
in the file.
v1.42.0
Compare Source
min()
andmax()
expressions are once again parsed as calculations as longas they contain only syntax that's allowed in calculation expressions. To
avoid the backwards-compatibility issues that were present in 1.40.0, they now
allow unitless numbers to be mixed with numbers with units just like the
global
min()
andmax()
functions. Similarly,+
and-
operations withinmin()
andmax()
functions allow unitless numbers to be mixed with numberswith units.
v1.41.1
Compare Source
var()
functions in calculations, because theycould potentially be replaced with sub-expressions that might need to be
parenthesized.
v1.41.0
Compare Source
Calculation values can now be combined with strings using the
+
operator.This was an error in 1.40.0, but this broke stylesheets that were relying on
$value + ""
expressions to generically convert values to strings. (Note thatthe Sass team recommends the use of
"#{$value}"
orinspect($value)
forthat use-case.)
The
selector.unify()
function now correctly returnsnull
when one selectoris a
:host
or:host-context
and the other is a selector that's guaranteedto be within the current shadow DOM. The
@extend
logic has been updatedaccordingly as well.
Fix a bug where extra whitespace in
min()
,max()
,clamp()
, andcalc()
expressions could cause bogus parse errors.
Fix a bug where the right-hand operand of a
-
in a calculation couldincorrectly be stripped of parentheses.
Dart API
SassCalculation.plus()
now allowsSassString
arguments.v1.40.1
Compare Source
Potentially breaking bug fix:
min()
andmax()
expressions outside ofcalculations now behave the same way they did in 1.39.2, returning unquoted
strings if they contain no Sass-specific features and calling the global
min()
andmax()
functions otherwise. Within calculations, they continue tobehave how they did in 1.40.0.
This fixes an unintended breaking change added in 1.40.0, wherein passing a
unitless number and a number without units to
min()
ormax()
now producesan error. Since this breakage affects a major Sass library, we're temporarily
reverting support for
min()
andmax()
calculations while we work ondesigning a longer-term fix.
v1.40.0
Compare Source
Add support for first-class
calc()
expressions (as well asclamp()
andplain-CSS
min()
andmax()
). This means:calc()
expressions will be parsed more thoroughly, and errors will behighlighted where they weren't before. This may break your stylesheets,
but only if they were already producing broken CSS.
calc()
expressions will be simplified where possible, and may even returnnumbers if they can be simplified away entirely.
calc()
expressions that can't be simplified to numbers return a new datatype known as "calculations".
Sass variables and functions can now be used in
calc()
expressions.New functions
meta.calc-name()
andmeta.calc-args()
can now inspectcalculations.
Dart API
Add a new value type,
SassCalculation
, that represents calculations.Add new
CalculationOperation
,CalculationOperator
, andCalculationInterpolation
types to represent types of arguments that mayexist as part of a calculation.
Add a new
Value.assertCalculation()
method.Add a new
Number.hasCompatibleUnits()
method.v1.39.2
Compare Source
@use ... with
would throw an error whenthat variable was defined in a module that also contained
@forward ... with
.v1.39.1
Compare Source
@at-root
does not work properly in nestedimports that contain
@use
rules. If the only@use
rules in the nestedimport are for built-in modules,
@at-root
should now work properly.Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), 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 has been generated by Mend Renovate. View repository job log here.