Update dependency sass to ~1.65.0
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
sass | devDependencies | minor | ~1.32 -> ~1.65.0 |
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the logs for more information.
Release Notes
sass/dart-sass
v1.65.1
- Update abs-percent deprecatedIn version to
1.65.0
.
v1.65.0
-
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. In future releases, this will emit a CSS abs() function to be resolved by the browser. This deprecation is namedabs-percent
.
v1.64.2
- No user-visible changes.
v1.64.1
Embedded Sass
- Fix a bug where a valid
SassCalculation.clamp()
with less than 3 arguments would throw an error.
v1.64.0
-
Comments that appear before or between
@use
and@forward
rules are now emitted 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 added in 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
- Fix a bug where nested relative
@imports
failed to load when using the deprecated functionsrender
orrenderSync
and those relative imports were loaded multiple times across different files.
v1.63.6
JavaScript API
- Fix
import sass from 'sass'
again after it was broken in the last release.
Embedded Sass
- Fix the
exports
declaration inpackage.json
.
v1.63.5
JavaScript API
- Fix a bug where loading the package through both CJS
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
JavaScript API
-
Re-enable support for
import sass from 'sass'
when loading the package from an ESM module in Node.js. However, this syntax is now deprecated; ESM users should useimport * 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
from the 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
JavaScript API
- Fix loading Sass as an ECMAScript module on Node.js.
v1.63.2
- No user-visible changes.
v1.63.1
- No user-visible changes.
v1.63.0
JavaScript API
- Dart Sass's JS API now supports running in the browser. Further details and 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 the pure 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 asass
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
- Fix a bug where
:has(+ &)
and related constructs would drop the leading combinator.
v1.62.0
-
Deprecate the use of multiple
!global
or!default
flags on the same variable. This deprecation is namedduplicate-var-flags
. -
Allow special numbers like
var()
orcalc()
in the global functions:grayscale()
,invert()
,saturate()
, andopacity()
. These are also native CSSfilter
functions. This is in addition to number values which were already 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
-
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
- The JS embedded host now loads files from the working directory when using the legacy API.
v1.60.0
-
Add support for the
pi
,e
,infinity
,-infinity
, andNaN
constants in calculations. 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
-
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
- No user-visible changes.
v1.59.1
- No user-visible changes.
v1.59.0
Command Line Interface
-
Added a new
--fatal-deprecation
flag that lets you treat a deprecation warning as an error. You can pass an individual deprecation ID (e.g.slash-div
) or you can pass a Dart Sass version to treat all deprecations initially emitted in that version or earlier as errors. -
New
--future-deprecation
flag that lets you opt into warning for use of certain features that will be deprecated in the future. At the moment, the only option is--future-deprecation=import
, which will emit warnings for Sass@import
rules, which are not yet deprecated, but will be in the future.
Dart API
-
New
Deprecation
enum, which contains the different current and future deprecations used by the new CLI flags. -
The
compile
methods now take infatalDeprecations
andfutureDeprecations
parameters, which work similarly to the CLI flags.
v1.58.3
- No user-visible changes.
v1.58.2
Command Line Interface
-
Add a timestamp to messages printed in
--watch
mode. -
Print better
calc()
-based suggestions for/
-as-division expression that contain calculation-incompatible constructs like unary minus.
v1.58.1
- Emit a unitless hue when serializing
hsl()
colors. Thedeg
unit is incompatible with IE, and while that officially falls outside our compatibility policy, it's better to lean towards greater compatibility.
v1.58.0
-
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 more combinators 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-
, a decimal 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
- The
--watch
flag will now track loads through calls tometa.load-css()
as long as their URLs are literal strings without any interpolation.
v1.57.1
- No user-visible changes.
v1.57.0
- Add a
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
-
Potentially breaking bug fix:
Callable.fromSignature()
andAsyncCallable.fromSignature()
now reject signatures with whitespace between the function name and parentheses.
v1.56.2
Embedded Sass
- The embedded compiler now supports version 1.2.0 of the embedded protocol.
v1.56.1
Embedded Sass
- Importer results now validate that
contents
is actually a string and whethersourceMapUrl
is an absolute URL.
v1.56.0
-
Potentially breaking change: To match the CSS spec, SassScript expressions beginning with
not
or(
are no longer supported at the beginning of parenthesized 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 now properly converted to equivalentdeg
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 Sass 2.0.0.See the Sass website for details.
-
Emit a deprecation warning when passing a
$weight
value with no units or with units other than%
tocolor.mix()
. This will be an error in Dart Sass 2.0.0.See the Sass website for details.
-
Emit a deprecation warning when passing
$n
values with units tolist.nth()
orlist.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 a deprecation warning. -
Fix a bug where
@extend
could behave unpredicatably when used along withmeta.load-css()
and shared modules that contained no CSS themselves but loaded CSS from other modules.
Dart API
- Emit a deprecation warning when passing a
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
-
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 they were within1e-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 longer treat 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 like they could be unary operations but they're actually parsed as binary operations. Either explicitly write$a - $b
or$a (-$b)
. See https://sass-lang.com/d/strict-unary for more details.
Dart API
-
Add an optional
argumentName
parameter toSassScriptException()
to make it easier to throw exceptions associated with particular argument names. -
Most APIs that previously returned
num
now returndouble
. All APIs continue to acceptnum
, although in Dart 2.0.0 these APIs will be changed to accept onlydouble
.
JS API
- Fix a bug in which certain warning spans would not have their properties accessible by the JS API.
v1.54.9
- Fix an incorrect span in certain
@media
query deprecation warnings.
v1.54.8
- No user-visible changes.
v1.54.7
- Add support for 32-bit ARM releases on Linux.
v1.54.6
- Fix a bug where a
@media
query could be incorrectly omitted from a stylesheet if it had multiple levels of nested@media
queries within it and the inner queries were mergeable but the outer query was not.
v1.54.5
-
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 similarly for 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 ignore units. -
Don't throw an error when the same module is
@forward
ed multiple times through a configured module.
Embedded Sass
- Rather than downloading the embedded compiler for the local platform on
install, the
sass-embedded
npm package now declares optional dependencies on platform-specific embedded compiler packages.
v1.54.4
- Improve error messages when passing incorrect units that are also out-of-bounds to various color functions.
v1.54.3
- Release a native ARM64 executable for Mac OS.
v1.54.2
- No user-visible changes.
v1.54.1
- When unifying selectors for
@extend
andselector.unify()
, ensure that:root
,:scope
,:host
, and:host-context
only appear at the beginning of complex selectors.
v1.54.0
-
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 opening parenthesis 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
- Add a top-level
fakeFromImport()
function for testing custom importers that useAsyncImporter.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
- Add support for calling
var()
with an empty second argument, such asvar(--side, )
.
JS API
- Fix a bug where
meta.load-css()
would sometimes resolve relative URLs incorrectly when called from a mixin using the legacy JS API.
Embedded Sass
- Respect npm's proxy settings when downloading the embedded Sass compiler.
v1.52.3
- Fix crash when trailing loud comments (
/* ... */
) appear twice in a row across two different imports which themselves imported the same file each.
v1.52.2
- Preserve location of trailing loud comments (
/* ... */
) instead of pushing the comment to the next line.
v1.52.1
Command Line Interface
- Fix a bug where
--watch
mode would close immediately in TTY mode. This was caused by our change to close--watch
when stdin was closed outside of TTY mode, which has been reverted for now while we work on a fix.
v1.52.0
-
Add support for arbitrary modifiers at the end of plain CSS imports, in addition to the existing
supports()
and media queries. Sass now allows any sequence 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 correctly return the number called on when it passes the assertion.
v1.51.0
-
Potentially breaking change: Change the order of maps returned by
map.deep-merge()
to match those returned bymap.merge()
. All keys that appeared 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
Embedded Sass
-
The JS embedded host and the embedded compiler will now properly avoid resolving imports relative to the current working directory unless
'.'
is passed 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
-
@extend
now treats [:where()
][:where()] the same as:is()
.
Command Line Interface
- Closing the standard input stream will now cause the
--watch
command to stop running.
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 legacy importers.
v1.49.11
- Add support for 64-bit ARM releases on Linux.
Embedded Sass
- The embedded compiler now correctly sets the
id
field for allOutboundMessage
s.
v1.49.10
-
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()
, andhsla()
function notation if they were defined using the corresponding notation. 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
Embedded Sass
- Fixed a bug where the legacy API could crash when passed an empty importer list.
v1.49.8
- Fixed a bug where some plain CSS imports would not be emitted.
JS API
- Fix a bug where inspecting the Sass module in the Node.js console crashed on Node 17.
Embedded Sass
- Fix a bug where source map URLs were incorrectly generated when passing importers to the legacy API.
v1.49.7
Embedded Sass
-
First stable release the
sass-embedded
npm package that contains the Node.js Embedded Host. -
First stable release of the
sass_embedded
pub package that contains the Embedded Dart Sass compiler.
v1.49.6
- No user-visible changes.
v1.49.5
- No user-visible changes.
v1.49.4
- No user-visible changes.
v1.49.3
- No user-visible changes.
v1.49.2
- No user-visible changes.
v1.49.1
- Add support for 64-bit ARM releases on Linux.
Embedded Sass
- The embedded compiler now correctly sets the
id
field for allOutboundMessage
s.
v1.49.0
- Fix a bug in
string.insert
with certain negative indices.
JS API
- Add support for the
sourceMapIncludeSources
option in the new JS API.
TypeScript Declarations
- Fix a bug where
LegacyPluginThis.options.linefeed
was typed to return abbreviations when it actually returned literal linefeed characters.
v1.48.0
JS API
-
Potentially breaking bug fix: Match the specification of the new JS API by
setting
LegacyResult.map
toundefined
rather thannull
.
TypeScript Declarations
- Add a declaration for the
NULL
constant.
v1.47.0
JS API
TypeScript Declarations
- Add declarations for the
TRUE
andFALSE
constants.
v1.46.0
JS API
-
Potentially breaking bug fix: Match the specification of the new JS API by
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 definitions with zero through six arguments before thedone
parameter. This makes it possible 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 returned by asynchronous functions to signal asynchronous errors. -
Add a
LegacyAsyncFunctionDone
type for thedone
callback that's passed toLegacyAsyncFunction
.
v1.45.2
JS API
-
Potentially breaking bug fix: Change the default value of the
separator
parameter fornew SassArgumentList()
to','
rather thannull
. This matches the API specification.
v1.45.1
-
Potentially breaking bug fix: Properly parse custom properties in
@supports
conditions. Note that this means that SassScript expressions on the right-hand side of custom property@supports
queries now need to be interpolated, as per https://sass-lang.com/d/css-vars. -
Potentially breaking bug fix: Fix a bug where
inspect()
was not properly printing nested, empty, bracketed lists.
v1.45.0
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 and return the result of compiling them to CSS. The async function returns aPromise
rather than using a callback-based API. -
compileString()
andcompileStringAsync()
functions that take a string of Sass source and compiles it to CSS. As above, the async function returns aPromise
. -
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 performance for 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 the legacy 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
- Suggest
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 treat unitless numbers as universally compatible. -
Fix a bug where
SassNumber.coerceToMatch()
andSassNumber.coerceValueToMatch()
wouldn't coerce single-unit numbers to match unitless numbers.
v1.43.5
-
Fix a bug where calculations with different operators were incorrectly considered equal.
-
Properly parse attribute selectors with empty namespaces.
JS API
- Print more detailed JS stack traces. This is mostly useful for the Sass team's own debugging purposes.
v1.43.4
JS API
- Fix a bug where the
logger
option was ignored for therender()
function.
v1.43.3
- Improve performance.
v1.43.2
- Improve the error message when the default namespace of a
@use
rule is not a valid identifier.
v1.42.1
- Fix a bug where Sass variables and function calls in calculations weren't being resolved correctly if there was a parenthesized interpolation elsewhere in the file.
v1.42.0
-
min()
andmax()
expressions are once again parsed as calculations as long as 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 globalmin()
andmax()
functions. Similarly,+
and-
operations withinmin()
andmax()
functions allow unitless numbers to be mixed with numbers with units.
v1.41.1
- Preserve parentheses around
var()
functions in calculations, because they could potentially be replaced with sub-expressions that might need to be parenthesized.
v1.41.0
-
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 that the Sass team recommends the use of"#{$value}"
orinspect($value)
for that use-case.) -
The
selector.unify()
function now correctly returnsnull
when one selector is a:host
or:host-context
and the other is a selector that's guaranteed to be within the current shadow DOM. The@extend
logic has been updated accordingly 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 could incorrectly be stripped of parentheses.
Dart API
-
SassCalculation.plus()
now allowsSassString
arguments.
v1.40.1
-
Potentially breaking bug fix:
min()
andmax()
expressions outside of calculations now behave the same way they did in 1.39.2, returning unquoted strings if they contain no Sass-specific features and calling the globalmin()
andmax()
functions otherwise. Within calculations, they continue to behave 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 produces an error. Since this breakage affects a major Sass library, we're temporarily reverting support formin()
andmax()
calculations while we work on designing a longer-term fix.
v1.40.0
-
Add support for first-class
calc()
expressions (as well asclamp()
and plain-CSSmin()
andmax()
). This means:-
calc()
expressions will be parsed more thoroughly, and errors will be highlighted 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 return numbers if they can be simplified away entirely. -
calc()
expressions that can't be simplified to numbers return a new data type known as "calculations". -
Sass variables and functions can now be used in
calc()
expressions. -
New functions
meta.calc-name()
andmeta.calc-args()
can now inspect calculations.
-
Dart API
-
Add a new value type,
SassCalculation
, that represents calculations. -
Add new
CalculationOperation
,CalculationOperator
, andCalculationInterpolation
types to represent types of arguments that may exist as part of a calculation. -
Add a new
Value.assertCalculation()
method. -
Add a new
Number.hasCompatibleUnits()
method.
v1.39.2
- Fix a bug where configuring with
@use ... with
would throw an error when that variable was defined in a module that also contained@forward ... with
.
v1.39.1
- Partial fix for a bug where
@at-root
does not work properly in nested imports that contain@use
rules. If the only@use
rules in the nested import are for built-in modules,@at-root
should now work properly.
v1.39.0
JS API
- Add a
charset
option that controls whether or not Sass emits a@charset
/BOM for non-ASCII stylesheets.
v1.38.2
- No user-visible changes
v1.38.1
- No user-visible changes
v1.38.0
-
In expanded mode, emit characters in Unicode private-use areas as escape sequences rather than literal characters.
-
Fix a bug where quotes would be omitted for an attribute selector whose value was a single backslash.
-
Properly consider numbers that begin with
.
as "plain CSS" for the purposes of parsing plain-CSSmin()
andmax()
functions. -
Allow
if
to be used as an unquoted string. -
Properly parse backslash escapes within
url()
expressions. -
Fix a couple bugs where
@extend
s could be marked as unsatisfied when multiple identical@extend
s extended selectors across@use
rules.
Command Line Interface
- Strip CRLF newlines from snippets of the original stylesheet that are included in the output when an error occurs.
JS API
-
Don't crash when a Windows path is returned by a custom Node importer at the same time as file contents.
-
Don't crash when an error occurs in a stylesheet loaded via a custom importer with a custom URL scheme.
Dart API
- Add a
SassArgumentList.keywordsWithoutMarking
getter to access the keyword arguments of an argument list without marking them accessed.
v1.37.5
- No user-visible changes.
v1.37.4
- No user-visible changes.
v1.37.3
- No user-visible changes.
v1.37.2
- No user-visible changes.
v1.37.1
- No user-visible changes.
v1.37.0
Dart API
-
Potentially breaking bug fix:
SassNumber.asSlash
,SassNumber.withSlash()
, andSassNumber.withoutSlash()
have been marked as@internal
. They were never intended to be used outside thesass
package. -
Potentially breaking bug fix:
SassException
has been marked as@sealed
to formally indicate that it's not intended to be extended outside of thesass
package. -
Add a
Value.withListContents()
method that returns a new Sass list with the same list separator and brackets as the current value, interpreted as a list.
v1.36.0
Dart API
-
Added
compileToResult()
,compileStringToResult()
,compileToResultAsync()
, andcompileStringToResultAsync()
methods. These are intended to replace the existingcompile*()
methods, which are now deprecated. Rather than returning a simple string, these return aCompileResult
object, which will allow us to add additional information about the compilation without having to introduce further deprecations.-
Instead of passing a
sourceMaps
callback tocompile*()
, passsourceMaps: true
tocompile*ToResult()
and accessCompileResult.sourceMap
. -
The
CompileResult
object exposes aloadedUrls
object which lists the canonical URLs accessed during a compilation. This information was previously unavailable except through the JS API.
-
v1.35.2
-
Potentially breaking bug fix: Properly throw an error for Unicode ranges that have too many
?
s after hexadecimal digits, such asU+12345??
. -
Potentially breaking bug fix: Fixed a bug where certain local variable declarations nested within multiple
@if
statements would incorrectly override a global variable. It's unlikely that any real stylesheets were relying on this bug, but if so they can simply add!global
to the variable declaration to preserve the old behavior. -
Potentially breaking bug fix: Fix a bug where imports of root-relative URLs (those that begin with
/
) in@import
rules would be passed to both Dart and JS importers asfile:
URLs. -
Properly support selector lists for the
$extendee
argument toselector.extend()
andselector.replace()
. -
Fix an edge case where
@extend
wouldn't affect a selector within a pseudo-selector such as:is()
that itself extended other selectors. -
Fix a race condition where
meta.load-css()
could trigger an internal error when running in asynchronous mode.
Dart API
- Use the
@internal
annotation to indicate whichValue
APIs are available for public use.
v1.35.1
- Fix a bug where the quiet dependency flag didn't silence warnings in some
stylesheets loaded using
@import
.
v1.35.0
-
Fix a couple bugs that could prevent some members from being found in certain files that use a mix of imports and the module system.
-
Fix incorrect recommendation for migrating division expressions that reference namespaced variables.
JS API
-
Add a
quietDeps
option which silences compiler warnings from stylesheets loaded through importers and load paths. -
Add a
verbose
option which causes the compiler to emit all deprecation warnings, not just 5 per feature.
v1.34.1
-
Fix a bug where
--update
would always compile any file that depends on a built-in module. -
Fix the URL for the
@-moz-document
deprecation message. -
Fix a bug with
@for
loops nested inside property declarations.
v1.34.0
-
Don't emit the same warning in the same location multiple times.
-
Cap deprecation warnings at 5 per feature by default.
Command Line Interface
-
Add a
--quiet-deps
flag which silences compiler warnings from stylesheets loaded through--load-path
s. -
Add a
--verbose
flag which causes the compiler to emit all deprecation warnings, not just 5 per feature.
Dart API
-
Add a
quietDeps
argument tocompile()
,compileString()
,compileAsync()
, andcompileStringAsync()
which silences compiler warnings from stylesheets loaded through importers, load paths, andpackage:
URLs. -
Add a
verbose
argument tocompile()
,compileString()
,compileAsync()
, andcompileStringAsync()
which causes the compiler to emit all deprecation warnings, not just 5 per feature.
v1.33.0
- Deprecate the use of
/
for division. The newmath.div()
function should be used instead. See this page for details.
-
Add a
list.slash()
function that returns a slash-separated list. -
Potentially breaking bug fix: The heuristics around when potentially slash-separated numbers are converted to slash-free numbers—for example, when
1/2
will be printed as0.5
rather than1/2
—have been slightly expanded. Previously, a number would be made slash-free if it was passed as an argument to a user-defined function, but not to a built-in function. Now it will be made slash-free in both cases. This is a behavioral change, but it's unlikely to affect any real-world stylesheets. -
[
:is()
][:is()] now behaves identically to:matches()
.
-
Fix a bug where non-integer numbers that were very close to integer values would be incorrectly formatted in CSS.
-
Fix a bug where very small number and very large negative numbers would be incorrectly formatted in CSS.
JS API
- The
this
context for importers now has afromImport
field, which istrue
if the importer is being invoked from an@import
andfalse
otherwise. Importers should only use this to determine whether to load import-only files.
Dart API
- Add an
Importer.fromImport
getter, which istrue
if the currentImporter.canonicalize()
call comes from an@import
rule andfalse
otherwise. Importers should only use this to determine whether to load import-only files.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.