Changelog
1.69.0
Add a meta.get-mixin()
function that returns a mixin as a first-class Sass
value.
Add a meta.apply()
mixin that includes a mixin value.
Add a meta.module-mixins()
function which returns a map from mixin names in
a module to the first-class mixins that belong to those names.
Add a meta.accepts-content()
function which returns whether or not a mixin
value 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.
Deprecation.calcInterp
since it was never actually emitted as a
deprecation.Changelog
1.68.0
abs-percent
deprecation.Non-filesystem importers can now set the nonCanonicalScheme
field, which
declares that one or more URL schemes (without :
) will never be used for
URLs returned by the canonicalize()
method.
Add a containingUrl
field to the canonicalize()
and findFileUrl()
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.
Add AsyncImporter.isNonCanonicalScheme
, which importers (async or sync) can
use 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 the
canonicalize()
method to the canonical URL of the stylesheet that contains
the 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.
The CalculationValue.interpolation
field is deprecated and will be removed
in 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
except
that "("
and ")"
will be added to the beginning and end of the string
values.
Properly include TypeScript types in the sass-embedded
package.
Changelog
1.67.0
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()
, and sign()
.
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()
and clamp()
are still forbidden,
users may continue to freely define functions whose names overlap with other
CSS calculations (including abs()
, min()
, max()
, and round()
whose
names 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 in
calculations. Instead of this, either use $variable
directly and ensure it
already 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.
Changelog
1.66.1
Changelog
1.66.0
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.
Changelog
1.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()
, and sign()
.
Deprecate explicitly passing the %
unit to the global abs()
function. In
future releases, this will emit a CSS abs() function to be resolved by the
browser. This deprecation is named abs-percent
.
Changelog
1.64.1
SassCalculation.clamp()
with less than 3 arguments
would throw an error.Changelog
1.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
.
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 a
SassCalculation
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.
@imports
failed to load when using the
deprecated functions render
or renderSync
and those relative imports were
loaded multiple times across different files.