Skip to content
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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 11, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sass 1.39.0 -> 1.69.5 age adoption passing confidence

Release Notes

sass/dart-sass (sass)

v1.69.5

Compare Source

JS API
  • Compatibility with Node.js 21.0.0.

v1.69.4

Compare Source

  • No user-visible changes.

v1.69.3

Compare Source

Embedded Sass
  • Fix TypeScript type locations in package.json.

v1.69.2

Compare Source

JS API
  • Fix a bug where Sass crashed when running in the browser if there was a global
    variable named process.

v1.69.1

Compare Source

  • No user-visible changes.

v1.69.0

Compare Source

  • 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.

Dart API
  • Deprecate Deprecation.calcInterp since it was never actually emitted as a
    deprecation.
Embedded Sass
  • Fix a rare race condition where the embedded compiler could freeze when a
    protocol error was immediately followed by another request.

v1.68.0

Compare Source

  • Fix the source spans associated with the abs-percent deprecation.
JS API
  • 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.

Dart API
  • 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.

Embedded Sass
  • 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.

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(), 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.

Embedded Sass
  • Substantially improve the embedded compiler's performance when compiling many
    files or files that require many importer or function call round-trips with
    the embedded host.

v1.66.1

Compare Source

JS API
  • Fix a bug where Sass compilation could crash in strict mode if passed a
    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

  • Update abs-percent deprecatedIn version to 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(), 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.

v1.64.2

Compare Source

  • No user-visible changes.

v1.64.1

Compare Source

Embedded Sass
  • Fix a bug where a valid SassCalculation.clamp() with less than 3 arguments
    would throw an error.

v1.64.0

Compare Source

  • 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 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.

Embedded Sass
  • Fix a bug where nested relative @imports failed to load when using the
    deprecated functions render or renderSync and those relative imports were
    loaded multiple times across different files.

v1.63.6

Compare Source

JavaScript API
  • Fix import sass from 'sass' again after it was broken in the last release.
Embedded Sass
  • Fix the exports declaration in package.json.

v1.63.5

Compare Source

JavaScript API
  • Fix a bug where loading the package through both CJS require() and ESM
    import 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 from
    an 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, and types 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

Compare Source

JavaScript API
  • Fix loading Sass as an ECMAScript module on Node.js.

v1.63.2

Compare Source

  • No user-visible changes.

v1.63.1

Compare Source

  • No user-visible changes.

v1.63.0

Compare Source

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 a
    sass executable with the same CLI as the sass 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

  • Fix a bug where :has(+ &) and related constructs would drop the leading
    combinator.

v1.62.0

Compare Source

  • Deprecate the use of multiple !global or !default flags on the same
    variable. This deprecation is named duplicate-var-flags.

  • Allow special numbers like var() or calc() in the global functions:
    grayscale(), invert(), saturate(), and opacity(). These are also
    native CSS filter 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

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
  • The JS embedded host now loads files from the working directory when using the
    legacy API.

v1.60.0

Compare Source

  • Add support for the pi, e, infinity, -infinity, and NaN 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, and NaN to calc()
    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

  • No user-visible changes.

v1.59.1

Compare Source

  • No user-visible changes.

v1.59.0

Compare Source

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 in fatalDeprecations and futureDeprecations
    parameters, which work similarly to the CLI flags.

v1.58.3

Compare Source

  • No user-visible changes.

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 that
    contain calculation-incompatible constructs like unary minus.

v1.58.1

Compare Source

  • Emit a unitless hue when serializing hsl() colors. The deg 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

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 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 to meta.load-css() as
    long as their URLs are literal strings without any interpolation.

v1.57.1

Compare Source

  • No user-visible changes.

v1.57.0

Compare Source

  • Add a split($string, $separator, $limit: null) function to sass: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() and
    AsyncCallable.fromSignature() now reject signatures with whitespace between
    the function name and parentheses.

v1.56.2

Compare Source

Embedded Sass

v1.56.1

Compare Source

Embedded Sass
  • Importer results now validate that contents is actually a string and whether
    sourceMapUrl 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 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 or turn are now
    properly converted to equivalent deg values for hsl(), hsla(),
    adjust-hue(), color.adjust(), and color.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 to
    color.adjust() or color.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 % to color.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 to list.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 in
    calc() 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 with
    meta.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 to
    Value.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-11th. Previously, numbers were considered equal if they
    were 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 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 returns
    1000000000000 instead of Infinity.

  • 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 to SassScriptException() to make it
    easier to throw exceptions associated with particular argument names.

  • Most APIs that previously returned num now return double. All APIs
    continue to accept num, although in Dart 2.0.0 these APIs will be changed
    to accept only double.

JS API
  • Fix a bug in which certain warning spans would not have their properties
    accessible by the JS API.

v1.54.9

Compare Source

  • Fix an incorrect span in certain @media query deprecation warnings.

v1.54.8

Compare Source

  • No user-visible changes.

v1.54.7

Compare Source

  • Add support for 32-bit ARM releases on Linux.

v1.54.6

Compare Source

  • 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

Compare Source

  • Properly consider a ~ c to be a superselector of a ~ b ~ c and a + b + c.

  • Properly consider b > c to be a superselector of a > 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 that
    random() currently ignores units. A future version will no longer ignore
    units.

  • Don't throw an error when the same module is @forwarded 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

Compare Source

  • Improve error messages when passing incorrect units that are also
    out-of-bounds to various color functions.

v1.54.3

Compare Source

  • Release a native ARM64 executable for Mac OS.

v1.54.2

Compare Source

  • No user-visible changes.

v1.54.1

Compare Source

  • When unifying selectors for @extend and selector.unify(), ensure that
    :root, :scope, :host, and :host-context only appear at the beginning
    of 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 opening
    parenthesis now produces a deprecation warning. In a future release, these
    will be interpreted as plain CSS instead.

  • Deprecate passing non-deg units to color.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 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

  • Add support for calling var() with an empty second argument, such as
    var(--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

Compare Source

  • 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

Compare Source

  • Preserve location of trailing loud comments (/* ... */) instead of pushing
    the comment to the next line.

v1.52.1

Compare Source

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

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 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() and SassNumber.assertNoUnits() now correctly
    return 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 by map.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

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 '.' 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

Compare Source

  • @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

Compare Source

  • Add support for 64-bit ARM releases on Linux.
Embedded Sass
  • The embedded compiler now correctly sets the id field for all
    OutboundMessages.

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 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

Compare Source

Embedded Sass
  • Fixed a bug where the legacy API could crash when passed an empty importer
    list.

v1.49.8

Compare Source

  • 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

Compare Source

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

Compare Source

  • No user-visible changes.

v1.49.5

Compare Source

  • No user-visible changes.

v1.49.4

Compare Source

  • No user-visible changes.

v1.49.3

Compare Source

  • No user-visible changes.

v1.49.2

Compare Source

  • No user-visible changes.

v1.49.1

Compare Source

  • Add support for 64-bit ARM releases on Linux.
Embedded Sass
  • The embedded compiler now correctly sets the id field for all
    OutboundMessages.

v1.49.0

Compare Source

  • 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

Compare Source

JS API
  • Potentially breaking bug fix: Match the specification of the new JS API by
    setting LegacyResult.map to undefined rather than null.
TypeScript Declarations
  • Add a declaration for the NULL constant.

v1.47.0

Compare Source

JS API
TypeScript Declarations
  • Add declarations for the TRUE and FALSE constants.

v1.46.0

Compare Source

JS API
  • Potentially breaking bug fix: Match the specification of the new JS API by
    passing undefined rather than null to Logger.warn() for an unset span.
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 the done 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 the done callback that's passed to
    LegacyAsyncFunction.

v1.45.2

Compare Source

JS API
  • Potentially breaking bug fix: Change the default value of the separator
    parameter for new SassArgumentList() to ',' rather than null. This
    matches 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 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

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() and compileAsync() functions that take Sass file paths and
    return the result of compiling them to CSS. The async function returns a
    Promise rather than using a callback-based API.

  • compileString() and compileStringAsync() functions that take a string of
    Sass 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 performance
    for applications that rely heavily on repeated @imports.

  • 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

Compare Source

  • Suggest calc() as an alternative in /-as-division deprecation messages.
Dart API
  • Add SassNumber.convert() and SassNumber.convertValue(). These work like
    SassNumber.coerce() and SassNumber.coerceValue(), except they don't treat
    unitless numbers as universally compatible.

  • Fix a bug where SassNumber.coerceToMatch() and
    SassNumber.coerceValueToMatch() wouldn't coerce single-unit numbers to
    match 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
  • Print more detailed JS stack traces. This is mostly useful for the Sass team's
    own debugging purposes.

v1.43.4

Compare Source

JS API
  • Fix a bug where the logger option was ignored for the render() function.

v1.43.3

Compare Source

  • Improve performance.

v1.43.2

Compare Source

  • Improve the error message when the default namespace of a @use rule is not
    a valid identifier.

v1.42.1

Compare Source

  • 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

Compare Source

  • min() and max() 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
    global min() and max() functions. Similarly, + and - operations within
    min() and max() functions allow unitless numbers to be mixed with numbers
    with units.

v1.41.1

Compare Source

  • 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

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 that
    the Sass team recommends the use of "#{$value}" or inspect($value) for
    that use-case.)

  • The selector.unify() function now correctly returns null 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(), and calc()
    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 allows SassString arguments.

v1.40.1

Compare Source

  • Potentially breaking bug fix: min() and max() 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 global
    min() and max() 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() or max() now produces
    an error. Since this breakage affects a major Sass library, we're temporarily
    reverting support for min() and max() calculations while we work on
    designing a longer-term fix.

v1.40.0

Compare Source

  • Add support for first-class calc() expressions (as well as clamp() and
    plain-CSS min() and max()). 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() and meta.calc-args() can now inspect
      calculations.

Dart API
  • Add a new value type, SassCalculation, that represents calculations.

  • Add new CalculationOperation, CalculationOperator, and
    CalculationInterpolation 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

Compare Source

  • 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

Compare Source

  • 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.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Sep 11, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sunya9/beta/29yjcMLPSr8FEfuN9db2SjuvV5qa
✅ Preview: https://beta-git-renovate-sass-1x-sunya9.vercel.app

@reg-suit
Copy link

reg-suit bot commented Sep 11, 2021

✨✨ That's perfect, there is no visual difference! ✨✨

Check out the report here.

@renovate renovate bot requested a review from sunya9 September 11, 2021 01:41
@renovate renovate bot force-pushed the renovate/sass-1.x branch from a823a5c to 09ae891 Compare September 14, 2021 01:02
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 09ae891 to 9baa257 Compare September 14, 2021 10:14
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 9baa257 to 351b7b0 Compare September 15, 2021 01:32
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 351b7b0 to 66aac10 Compare September 16, 2021 23:14
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 66aac10 to bc30929 Compare September 21, 2021 01:04
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from bc30929 to 2614b6d Compare September 22, 2021 08:15
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 2614b6d to 6c2c778 Compare October 13, 2021 23:06
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 6c2c778 to a0baac3 Compare October 21, 2021 21:16
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from a0baac3 to 179a488 Compare October 26, 2021 22:18
@renovate renovate bot force-pushed the renovate/sass-1.x branch from af8e5a8 to 2e6cdd9 Compare August 17, 2023 20:14
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 2e6cdd9 to ccc4054 Compare August 18, 2023 23:23
@renovate renovate bot force-pushed the renovate/sass-1.x branch from ccc4054 to 70711be Compare September 14, 2023 01:08
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 70711be to 0be8049 Compare September 21, 2023 03:54
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 0be8049 to f69e183 Compare October 6, 2023 00:12
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from f69e183 to 394d95f Compare October 10, 2023 00:53
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 394d95f to 1302656 Compare October 10, 2023 19:36
@renovate 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 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 renovate bot force-pushed the renovate/sass-1.x branch from 1302656 to 9d57a63 Compare October 12, 2023 00:29
@renovate renovate bot force-pushed the renovate/sass-1.x branch from 9d57a63 to 5e9adc7 Compare October 18, 2023 02:02
@renovate 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 renovate bot force-pushed the renovate/sass-1.x branch from 5e9adc7 to 408a44d Compare October 26, 2023 01:45
@renovate 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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant