Update all dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
autoprefixer	10.4.13 → 10.5.2
prettier (source)	2.8.1 → 2.8.8
sass	1.57.1 → 1.101.0
stylelint-config-prettier	9.0.4 → 9.0.5

---

Release Notes

postcss/autoprefixer (autoprefixer)

v10.5.2

Compare Source

• Moved -webkit-fill-available before -moz-available, so Firefox
  will use -webkit- version which is closer to stretch.

v10.5.1

Compare Source

• Fixed grid-area span reset for overriding areas (by @​puneetdixit200).

v10.5.0

Compare Source

• Added mask-position-x and mask-position-y support (by @​toporek).

v10.4.27

Compare Source

• Removed development key from package.json.

v10.4.26

Compare Source

• Reduced package size.

v10.4.25

Compare Source

• Fixed broken gradients on CSS Custom Properties (by @​serger777).

v10.4.24

Compare Source

• Made Autoprefixer a little faster (by @​Cherry).

v10.4.23

Compare Source

• Reduced dependencies (by @​hyperz111).

v10.4.22

Compare Source

• Fixed stretch prefixes on new Can I Use database.
• Updated fraction.js.

v10.4.21

Compare Source

• Fixed old -moz- prefix for :placeholder-shown (by @​Marukome0743).

v10.4.20

Compare Source

• Fixed fit-content prefix for Firefox.

v10.4.19

Compare Source

• Removed end value has mixed support, consider using flex-end warning
  since end/start now have good support.

v10.4.18

Compare Source

• Fixed removing -webkit-box-orient on -webkit-line-clamp (@​Goodwine).

v10.4.17

Compare Source

• Fixed user-select: contain prefixes.

v10.4.16

Compare Source

• Improved performance (by Romain Menke).
• Fixed docs (by Christian Oliff).

v10.4.15

Compare Source

• Fixed ::backdrop prefixes (by 一丝).
• Fixed docs (by Christian Oliff).

v10.4.14

Compare Source

• Improved startup time and reduced JS bundle size (by Kārlis Gaņģis).

prettier/prettier (prettier)

v2.8.8

Compare Source

This version is a republished version of v2.8.7.
A bad version was accidentally published and it can't be unpublished, apologies for the churn.

v2.8.7

Compare Source

diff

Allow multiple decorators on same getter/setter (#​14584 by @​fisker)

// Input
class A {
  @​decorator()
  get foo () {}
  
  @​decorator()
  set foo (value) {}
}

// Prettier 2.8.6
SyntaxError: Decorators cannot be applied to multiple get/set accessors of the same name. (5:3)
  3 |   get foo () {}
  4 |   
> 5 |   @​decorator()
    |   ^^^^^^^^^^^^
  6 |   set foo (value) {}
  7 | }

// Prettier 2.8.7
class A {
  @​decorator()
  get foo() {}

  @​decorator()
  set foo(value) {}
}

v2.8.6

Compare Source

diff

Allow decorators on private members and class expressions (#​14548 by @​fisker)

// Input
class A {
  @​decorator()
  #privateMethod () {}
}

// Prettier 2.8.5
SyntaxError: Decorators are not valid here. (2:3)
  1 | class A {
> 2 |   @​decorator()
    |   ^^^^^^^^^^^^
  3 |   #privateMethod () {}
  4 | }

// Prettier 2.8.6
class A {
  @​decorator()
  #privateMethod() {}
}

v2.8.5

Compare Source

diff

Support TypeScript 5.0 (#​14391 by @​fisker, #​13819 by @​fisker, @​sosukesuzuki)

TypeScript 5.0 introduces two new syntactic features:

• const modifiers for type parameters
• export type * declarations

Add missing parentheses for decorator (#​14393 by @​fisker)

// Input
class Person {
  @​(myDecoratorArray[0])
  greet() {}
}

// Prettier 2.8.4
class Person {
  @​myDecoratorArray[0]
  greet() {}
}

// Prettier 2.8.5
class Person {
  @​(myDecoratorArray[0])
  greet() {}
}

Add parentheses for TypeofTypeAnnotation to improve readability (#​14458 by @​fisker)

// Input
type A = (typeof node.children)[];

// Prettier 2.8.4
type A = typeof node.children[];

// Prettier 2.8.5
type A = (typeof node.children)[];

Support max_line_length=off when parsing .editorconfig (#​14516 by @​josephfrazier)

If an .editorconfig file is in your project and it sets max_line_length=off for the file you're formatting,
it will be interpreted as a printWidth of Infinity rather than being ignored
(which previously resulted in the default printWidth of 80 being applied, if not overridden by Prettier-specific configuration).

<!-- Input -->
<div className='HelloWorld' title={`You are visitor number ${ num }`} onMouseOver={onMouseOver}/>

<!-- Prettier 2.8.4 -->
<div
  className="HelloWorld"
  title={`You are visitor number ${num}`}
  onMouseOver={onMouseOver}
/>;

<!-- Prettier 2.8.5 -->
<div className="HelloWorld" title={`You are visitor number ${num}`} onMouseOver={onMouseOver} />;

v2.8.4

Compare Source

diff

Fix leading comments in mapped types with readonly (#​13427 by @​thorn0, @​sosukesuzuki)

// Input
type Type = {
  // comment
  readonly [key in Foo];
};

// Prettier 2.8.3
type Type = {
  readonly // comment
  [key in Foo];
};

// Prettier 2.8.4
type Type = {
  // comment
  readonly [key in Foo];
};

Group params in opening block statements (#​14067 by @​jamescdavis)

This is a follow-up to #​13930 to establish wrapping consistency between opening block statements and else blocks by
grouping params in opening blocks. This causes params to break to a new line together and not be split across lines
unless the length of params exceeds the print width. This also updates the else block wrapping to behave exactly the
same as opening blocks.

{{! Input }}
{{#block param param param param param param param param param param as |blockParam|}}
  Hello
{{else block param param param param param param param param param param as |blockParam|}}
  There
{{/block}}

{{! Prettier 2.8.3 }}
{{#block
  param
  param
  param
  param
  param
  param
  param
  param
  param
  param
  as |blockParam|
}}
  Hello
{{else block param
param
param
param
param
param
param
param
param
param}}
  There
{{/block}}

{{! Prettier 2.8.4 }}
{{#block
  param param param param param param param param param param
  as |blockParam|
}}
  Hello
{{else block
  param param param param param param param param param param
  as |blockParam|
}}
  There
{{/block}}

Ignore files in .sl/ (#​14206 by @​bolinfest)

In Sapling SCM, .sl/ is the folder where it stores its state, analogous to .git/ in Git. It should be ignored in Prettier like the other SCM folders.

Recognize @satisfies in Closure-style type casts (#​14262 by @​fisker)

// Input
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

// Prettier 2.8.3
const a = /** @&#8203;satisfies {Record<string, string>} */ { hello: 1337 };
const b = /** @&#8203;type {Record<string, string>} */ ({ hello: 1337 });

// Prettier 2.8.4
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

Fix parens in inferred function return types with extends (#​14279 by @​fisker)

// Input
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;

// Prettier 2.8.3 (First format)
type Foo<T> = T extends (a) => a is infer R extends string ? R : never;

// Prettier 2.8.3 (Second format)
SyntaxError: '?' expected. 

// Prettier 2.8.4
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;

v2.8.3

Compare Source

diff

Allow self-closing tags on custom elements (#​14170 by @​fisker)

See Angular v15.1.0 release note for details.

// Input
<app-test/>

// Prettier 2.8.2
SyntaxError: Only void and foreign elements can be self closed "app-test" (1:1)
> 1 | <app-test/>
    | ^^^^^^^^^
  2 |

// Prettier 2.8.3
<app-test />

v2.8.2

Compare Source

diff

Don't lowercase link references (#​13155 by @​DerekNonGeneric & @​fisker)

<!-- Input -->
We now don't strictly follow the release notes format suggested by [Keep a Changelog].

[Keep a Changelog]: https://example.com/

<!-- Prettier 2.8.1 -->
We now don't strictly follow the release notes format suggested by [Keep a Changelog].

[keep a changelog]: https://example.com/
<!--
^^^^^^^^^^^^^^^^^^ lowercased
-->

<!-- Prettier 2.8.2 -->
<Same as input>

Preserve self-closing tags (#​13691 by @​dcyriller)

{{! Input }}
<div />
<div></div>
<custom-component />
<custom-component></custom-component>
<i />
<i></i>
<Component />
<Component></Component>

{{! Prettier 2.8.1 }}
<div></div>
<div></div>
<custom-component></custom-component>
<custom-component></custom-component>
<i></i>
<i></i>
<Component />
<Component />

{{! Prettier 2.8.2 }}
<div />
<div></div>
<custom-component />
<custom-component></custom-component>
<i />
<i></i>
<Component />
<Component />

Allow custom "else if"-like blocks with block params (#​13930 by @​jamescdavis)

#​13507 added support for custom block keywords used with else, but failed to allow block params. This updates printer-glimmer to allow block params with custom "else if"-like blocks.

{{! Input }}
{{#when isAtWork as |work|}}
  Ship that
  {{work}}!
{{else when isReading as |book|}}
  You can finish
  {{book}}
  eventually...
{{else}}
  Go to bed!
{{/when}}

{{! Prettier 2.8.1 }}
{{#when isAtWork as |work|}}
  Ship that
  {{work}}!
{{else when isReading}}
  You can finish
  {{book}}
  eventually...
{{else}}
  Go to bed!
{{/when}}

{{! Prettier 2.8.2 }}
{{#when isAtWork as |work|}}
  Ship that
  {{work}}!
{{else when isReading as |book|}}
  You can finish
  {{book}}
  eventually...
{{else}}
  Go to bed!
{{/when}}

Preserve empty lines between nested SCSS maps (#​13931 by @​jneander)

/* Input */
$map: (
  'one': (
     'key': 'value',
  ),

  'two': (
     'key': 'value',
  ),
)

/* Prettier 2.8.1 */
$map: (
  'one': (
     'key': 'value',
  ),
  'two': (
     'key': 'value',
  ),
)

/* Prettier 2.8.2 */
$map: (
  'one': (
     'key': 'value',
  ),

  'two': (
     'key': 'value',
  ),
)

Fix missing parentheses when an expression statement starts with let[ (#​14000, #​14044 by @​fisker, @​thorn0)

// Input
(let[0] = 2);

// Prettier 2.8.1
let[0] = 2;

// Prettier 2.8.1 (second format)
SyntaxError: Unexpected token (1:5)
> 1 | let[0] = 2;
    |     ^
  2 |

// Prettier 2.8.2
(let)[0] = 2;

Fix semicolon duplicated at the end of LESS file (#​14007 by @​mvorisek)

// Input
@​variable: {
  field: something;
};

// Prettier 2.8.1
@​variable: {
  field: something;
}; ;

// Prettier 2.8.2
@​variable: {
  field: something;
};

Fix no space after unary minus when followed by opening parenthesis in LESS (#​14008 by @​mvorisek)

// Input
.unary_minus_single {
  margin: -(@​a);
}

.unary_minus_multi {
  margin: 0 -(@​a);
}

.binary_minus {
  margin: 0 - (@​a);
}

// Prettier 2.8.1
.unary_minus_single {
  margin: - (@​a);
}

.unary_minus_multi {
  margin: 0 - (@​a);
}

.binary_minus {
  margin: 0 - (@​a);
}

// Prettier 2.8.2
.unary_minus_single {
  margin: -(@​a);
}

.unary_minus_multi {
  margin: 0 -(@​a);
}

.binary_minus {
  margin: 0 - (@​a);
}

Do not change case of property name if inside a variable declaration in LESS (#​14034 by @​mvorisek)

// Input
@​var: {
  preserveCase: 0;
};

// Prettier 2.8.1
@​var: {
  preservecase: 0;
};

// Prettier 2.8.2
@​var: {
  preserveCase: 0;
};

Fix formatting for auto-accessors with comments (#​14038 by @​fisker)

// Input
class A {
  @​dec()
  // comment
  accessor b;
}

// Prettier 2.8.1
class A {
  @​dec()
  accessor // comment
  b;
}

// Prettier 2.8.1 (second format)
class A {
  @​dec()
  accessor; // comment
  b;
}

// Prettier 2.8.2
class A {
  @​dec()
  // comment
  accessor b;
}

Add parentheses for TSTypeQuery to improve readability (#​14042 by @​onishi-kohei)

// Input
a as (typeof node.children)[number]
a as (typeof node.children)[]
a as ((typeof node.children)[number])[]

// Prettier 2.8.1
a as typeof node.children[number];
a as typeof node.children[];
a as typeof node.children[number][];

// Prettier 2.8.2
a as (typeof node.children)[number];
a as (typeof node.children)[];
a as (typeof node.children)[number][];

Fix displacing of comments in default switch case (#​14047 by @​thorn0)

It was a regression in Prettier 2.6.0.

// Input
switch (state) {
  default:
    result = state; // no change
    break;
}

// Prettier 2.8.1
switch (state) {
  default: // no change
    result = state;
    break;
}

// Prettier 2.8.2
switch (state) {
  default:
    result = state; // no change
    break;
}

Support type annotations on auto accessors via babel-ts (#​14049 by @​sosukesuzuki)

The bug that @babel/parser cannot parse auto accessors with type annotations has been fixed. So we now support it via babel-ts parser.

class Foo {
  accessor prop: number;
}

Fix formatting of empty type parameters (#​14073 by @​fisker)

// Input
const foo: bar</* comment */> = () => baz;

// Prettier 2.8.1
Error: Comment "comment" was not printed. Please report this error!

// Prettier 2.8.2
const foo: bar</* comment */> = () => baz;

Add parentheses to head of ExpressionStatement instead of the whole statement (#​14077 by @​fisker)

// Input
({}).toString.call(foo) === "[object Array]"
  ? foo.forEach(iterateArray)
  : iterateObject(foo);

// Prettier 2.8.1
({}.toString.call(foo) === "[object Array]"
  ? foo.forEach(iterateArray)
  : iterateObject(foo));

// Prettier 2.8.2
({}).toString.call(foo.forEach) === "[object Array]"
  ? foo.forEach(iterateArray)
  : iterateObject(foo);

Fix comments after directive (#​14081 by @​fisker)

// Input
"use strict" /* comment */;

// Prettier 2.8.1 (with other js parsers except `babel`)
Error: Comment "comment" was not printed. Please report this error!

// Prettier 2.8.2
<Same as input>

Fix formatting for comments inside JSX attribute (#​14082 by @​fisker)

// Input
function MyFunctionComponent() {
  <button label=/*old*/"new">button</button>
}

// Prettier 2.8.1
Error: Comment "old" was not printed. Please report this error!

// Prettier 2.8.2
function MyFunctionComponent() {
  <button label=/*old*/ "new">button</button>;
}

Quote numeric keys for json-stringify parser (#​14083 by @​fisker)

// Input
{0: 'value'}

// Prettier 2.8.1
{
  0: "value"
}

// Prettier 2.8.2
{
  "0": "value"
}

Fix removing commas from function arguments in maps (#​14089 by @​sosukesuzuki)

/* Input */
$foo: map-fn(
  (
    "#{prop}": inner-fn($first, $second),
  )
);

/* Prettier 2.8.1 */
$foo: map-fn(("#{prop}": inner-fn($first $second)));

/* Prettier 2.8.2 */
$foo: map-fn(
  (
    "#{prop}": inner-fn($first, $second),
  )
);

Do not insert space in LESS property access (#​14103 by @​fisker)

// Input
a {
  color: @​colors[@​white];
}

// Prettier 2.8.1
a {
  color: @​colors[ @​white];
}

// Prettier 2.8.2
<Same as input>

sass/dart-sass (sass)

v1.101.0

Compare Source

• Potentially breaking bug fix: The Node package importer now properly
  supports resolving import-only variants of Sass files declared in the
  exports, sass, and style fields of package.json. Previously, these
  files were ignored even when loaded via @import, so any code relying on
  loading module-system-only files this way may break.

v1.100.0

Compare Source

• Writing two compound selectors adjacent to one another without any whitespace
  between them, such as [class]a, is now deprecated. This was always an error
  in CSS and Sass only supported it by mistake.

  See the Sass website for
  details.

v1.99.0

Compare Source

• Add support for parent selectors (&) at the root of the document. These are
  emitted as-is in the CSS output, where they're interpreted as the scoping
  root.

• User-defined functions named calc or clamp are no longer forbidden. If
  such a function exists without a namespace in the current module, it will be
  used instead of the built-in calc() or clamp() function.

• User-defined functions whose names begin with - and end with -expression,
  -url, -and, -or, or -not are no longer forbidden. These were
  originally intended to match vendor prefixes, but in practice no vendor
  prefixes for these functions ever existed in real browsers.

• User-defined functions named EXPRESSION, URL, and ELEMENT, those that
  begin with - and end with -ELEMENT, as well as the same names with some
  lowercase letters are now deprecated, These are names conflict with plain CSS
  functions that have special syntax.

  See the Sass website for details.

• In a future release, calls to functions whose names begin with - and end
  with -expression and -url will no longer have special parsing. For now,
  these calls are deprecated if their behavior will change in the future.

  See the Sass website for details.

• Calls to functions whose names begin with - and end with -progid:... are
  deprecated.

  See the Sass website for details.

v1.98.0

Compare Source

Command-Line Interface

• Gracefully handle dependency loops in --watch mode.

Dart API

• Add a const Logger.defaultLogger field. This provides a logger that emits to
  standard error or the browser console, but automatically chooses whether to
  use terminal colors.

JavaScript API

• Fix a crash when manually constructing a SassCalculation for 'calc' with
  an argument that can't be simplified.

• Properly emit deprecation warnings as text rather than StringBuffer objects
  when running in a browser.

• Emit colored warnings and other messages on the console when running in a
  browser.

v1.97.3

Compare Source

• Fix a bug where nesting an at-rule within multiple style rules in plain CSS
  could cause outer style rules to be omitted.

v1.97.2

Compare Source

• Additional fixes for implicit configuration when nested imports are involved.

v1.97.1

Compare Source

• Fix a bug with the new CSS-style if() syntax where values would be evaluated
  even if their conditions didn't match.

v1.97.0

Compare Source

• Add support for the display-p3-linear color space.

v1.96.0

Compare Source

• Allow numbers with complex units (more than one numerator unit or more than
  zero denominator units) to be emitted to CSS. These are now emitted as
  calc() expressions, which now support complex units in plain CSS.

v1.95.1

Compare Source

• No user-visible changes.

v1.95.0

Compare Source

• Add support for the CSS-style if() function. In addition to supporting the
  plain CSS syntax, this also supports a sass() query that takes a Sass
  expression that evaluates to true or false at preprocessing time depending
  on whether the Sass value is truthy. If there are no plain-CSS queries, the
  function will return the first value whose query returns true during
  preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3)
  returns 2.

• The old Sass if() syntax is now deprecated. Users are encouraged to migrate
  to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to
  if(sass($condition): $if-true; else: $if-false).

  See the Sass website for details.

• Plain-CSS if() functions are now considered "special numbers", meaning that
  they can be used in place of arguments to CSS color functions.

• Plain-CSS if() functions and attr() functions are now considered "special
  variable strings" (like var()), meaning they can now be used in place of
  multiple arguments or syntax fragments in various CSS functions.

v1.94.3

Compare Source

• Fix the span reported for standalone % expressions followed by whitespace.

v1.94.2

Compare Source

Command-Line Interface

• Using --fatal-deprecation <version> no longer emits warnings about
  deprecations that are obsolete.

Dart API

• Deprecation.forVersion now excludes obsolete deprecations from the set it
  returns.

JS API

• Excludes obsolete deprecations from fatalDeprecations when a Version is
  passed.

Node.js Embedded Host

• Fix a bug where a variable could be used before it was initialized during
  async compilation.

v1.94.1

Compare Source

• No user-visible changes.

v1.94.0

Compare Source

• Potentially breaking compatibility fix: @function rules whose names
  begin with -- are now parsed as unknown at-rules to support the plain CSS
  @function rule. Within this rule, the result property is parsed as raw
  CSS just like custom properties.

• Potentially breaking compatibility fix: @mixin rules whose names begin
  with -- are now errors. These are not yet parsed as unknown at-rules because
  no browser currently supports CSS mixins.

v1.93.3

Compare Source

• Fix a performance regression that was introduced in 1.92.0.

v1.93.2

Compare Source

• No user-visible changes.

JavaScript API

• Fix another error in the release process for @sass/types.

v1.93.1

Compare Source

• No user-visible changes.

JavaScript API

• Fix an error in the release process for @sass/types.

v1.93.0

Compare Source

• Fix a crash when a style rule contains a nested @import, and the loaded file
  @uses a user-defined module as well as @includes a top-level mixin which
  emits top-level declarations.

JavaScript API

• Release a @sass/types package which contains the type annotations used by
  both the sass and sass-embedded package without any additional code or
  dependencies.

v1.92.1

Compare Source

• Fix a bug where variable definitions from one imported, forwarded module
  would not be passed as implicit configuration to a later imported, forwarded
  module.

v1.92.0

Compare Source

• Breaking change: Emit declarations, childless at-rules, and comments in
  the order they appear in the source even when they're interleaved with nested
  rules. This obsoletes the mixed-decls deprecation.

• Breaking change: The function name type() is now fully reserved for the
  plain CSS function. This means that @function definitions with the name
  type will produce errors, while function calls will be parsed as special
  function strings.

• Configuring private variables using @use ... with, @forward ... with, and
  meta.load-css(..., $with: ...) is now deprecated. Private variables were
  always intended to be fully encapsulated within the module that defines them,
  and this helps enforce that encapsulation.

• Fix a bug where @extend rules loaded through a mixture of @import and
  @use rules could fail to apply correctly.

Command-Line Interface

• In --watch mode, delete the source map when the associated source file is
  deleted.

v1.91.0

Compare Source

• Potentially breaking change: meta.inspect() (as well as other systems
  that use it such as @debug and certain error messages) now emits numbers
  with as high precision as is available instead of rounding to the nearest
  1e⁻¹⁰ as we do when serializing to CSS. This better fits the purpose of
  meta.inspect(), which is to provide full information about the structure of
  a Sass value.

• Passing a rest argument ($arg...) before a positional or named argument when
  calling a function or mixin is now deprecated. This was always outside the
  specified syntax, but it was historically treated the same as passing the rest
  argument at the end of the argument list whether or not that matched the
  visual order of the arguments.

v1.90.0

Compare Source

• Allow a @forwarded module to be loaded with a configuration when that module
  has already been loaded with a different configuration and the module
  doesn't define any variables that would have been configured anyway.

v1.89.2

Compare Source

Embedded Host

• Fixed a compilation error caused by an outdated buf dependency.

v1.89.1

Compare Source

• No user-visible changes.

v1.89.0

Compare Source

• Allow the Node package importer to load files even when there are multiple
  potential resolutions, as long as those resolutions all point to the same
  file.

v1.88.0

Compare Source

• Allow custom properties with empty values (such as --var:;).

• Fix a bug when calculating source spans for interpolations.

Dart and JS APIs

• Potentially breaking bug fix: Throw an error when passing a function or
  mixin object from one compilation to another.

Dart API

• Deprecate passing a relative URL to compileString() and related functions.

v1.87.0

Compare Source

• Potentially breaking bug fix: When a plain CSS file with a top-level
  nesting selector & is loaded into a nested Sass context via
  meta.load-css() or @import, Sass now emits plain CSS nesting rather than
  incorrectly combining it with the parent selector using a descendant
  combinator.

v1.86.3

Compare Source

• Fix a bug introduced in 1.86.1 where Sass fails to resolve paths starting with
  a .. segment.

v1.86.2

Compare Source

• No user-visible changes.

v1.86.1

Compare Source

• Improve the performance of file: URL case canonicalization on Windows and
  Mac OS.

v1.86.0

Compare Source

• Add support for % as an expression in its own right. It will still be parsed
  as the modulo operator when between two other expressions, but in any other
  context it will be an expression whose value is the unquoted string %.

• Consider attr() to be a special number function that can be used as a
  channel in color functions.

• Deprecate user-defined functions named type() so that we can eventually
  support the new CSS type() function.

Dart API

• Increase the minimum Dart SDK to 3.6.0.

v1.85.1

Compare Source

• Fix a bug where global Sass functions whose names overlap with CSS math
  functions could incorrectly be treated as CSS math functions even though they
  used Sass-only features, causing compilation failures. For example,
  round(-$var / 2) previously threw an error but now works as intended.

v1.85.0

Compare Source

• No longer fully trim redundant selectors generated by @extend. This caused
  unacceptable performance issues for certain heavy users of @extend. We'll
  try to find a more performant way to accomplish it in the future.

v1.84.0

Compare Source

• Allow newlines in whitespace in the indented syntax.

• Potentially breaking bug fix: Selectors with unmatched brackets now always
  produce a parser error. Previously, some edge cases like [foo#{"]:is(bar"}) {a: b} would compile without error, but this was an unintentional bug.

• Fix a bug in which various Color Level 4 functions weren't allowed in plain
  CSS.

• Fix the error message for @extend without a selector and possibly other
  parsing edge-cases in contexts that allow interpolation.

Embedded Host

• Fixed the implementation of the SassBoolean type to adhere to the spec,
  now using a class instead of an interface.

v1.83.4

Compare Source

• No user-visible changes.

v1.83.3

Compare Source

• No user-visible changes.

v1.83.2

Compare Source

• Properly display deprecation IDs for the JS Sass API.

• Don't display deprecation IDs for user-defined deprecations.

v1.83.1

Compare Source

• Fix a bug where --quiet-deps would get deactivated for @content blocks,
  even when those blocks were entirely contained within dependencies.

• Include deprecation IDs in deprecation warnings to make it easier to determine
  what to pass to --silence-deprecation or --fatal-deprecation.

v1.83.0

Compare Source

• Allow trailing commas in all argument and parameter lists.

v1.82.0

Compare Source

Command-Line Interface

• Improve --watch mode reliability when making multiple changes at once, such
  as checking out a different Git branch.

• Parse the calc-size() function as a calculation now that it's supported in
  some browsers.

Dart API

• Add a SassCalculation.calcSize() function.

v1.81.1

Compare Source

• No user-visible changes.

v1.81.0

Compare Source

• Fix a few cases where deprecation warnings weren't being emitted for global
  built-in functions whose names overlap with CSS calculations.

• Add support for the CSS round() calculation with a single argument, as long
  as that argument might be a unitless number.

v1.80.7

Compare Source

Embedded Host

• Don't treat 0 as undefined for the green and blue channels in the
  LegacyColor constructor.

v1.80.6

Compare Source

Command-Line Interface

• Make @parcel/watcher an optional dependency so this can still be installed
  on operating systems where it's unavailable.

v1.80.5

Compare Source

Embedded Host

• Don't produce phantom @import deprecations when using an importer with the
  legacy API.

v1.80.4

Compare Source

• No user-visible changes.

v1.80.3

Compare Source

• Fix a bug where @import url("...") would crash in plain CSS files.

• Improve consistency of how warnings are emitted by different parts of the
  compiler. This should result in minimal user-visible changes, but different
  types of warnings should now respond more reliably to flags like --quiet,
  --verbose, and --silence-deprecation.

v1.80.2

Compare Source

• Fix a bug where deprecation warnings were incorrectly emitted for the
  plain-CSS invert() function.

v1.80.1

Compare Source

• Fix a bug where repeated deprecation warnings were not automatically limited.

v1.80.0

Compare Source

• @import is now officially deprecated, as are global built-in functions that
  are available within built-in modules. See the Sass blog post for more
  details on the deprecation process.

Embedded Host

• Fix an error that would sometimes occur when deprecation warnings were
  emitted when using a custom importer with the legacy API.

v1.79.6

Compare Source

• Fix a bug where Sass would add an extra */ after loud comments with
  whitespace after an explicit */ in the indented syntax.

• Potentially breaking bug fix: Adding text after an explicit */ in the
  indented syntax is now an error, rather than silently generating invalid CSS.

Embedded Host

• Properly export the SassBoolean type.

v1.79.5

Compare Source

• Changes to how selector.unify() and @extend combine selectors:

  • The relative order of pseudo-classes (like :hover) and pseudo-elements
    (like ::before) within each original selector is now preserved when
    they're combined.

  • Pseudo selectors are now consistently placed at the end of the combined
    selector, regardless of which selector they came from. Previously, this
    reordering only applied to pseudo-selectors in the second selector.

• Tweak the color transformation matrices for OKLab and OKLCH to match the
  newer, more accurate values in the CSS spec.

• Fix a slight inaccuracy case when converting to srgb-linear and
  display-p3.

• Potentially breaking bug fix: math.unit() now wraps multiple denominator
  units in parentheses. For example, px/(em*em) instead of px/em*em.

Command-Line Interface

• Use @parcel/watcher to watch the filesystem when running from JavaScript and
  not using --poll. This should mitigate more frequent failures users have
  been seeing since version 4.0.0 of Chokidar, our previous watching tool, was
  released.

JS API

• Fix SassColor.interpolate() to allow an undefined options parameter, as
  the types indicate.

Embedded Sass

• Properly pass missing color channel values to and from custom functions.

v1.79.4

Compare Source

JS API

• Fix a bug where passing green or blue to color.change() for legacy
  colors would fail.

v1.79.3

Compare Source

• Update the $channel parameter in the suggested replacement for
  color.red(), color.green(), color.blue(), color.hue(),
  color.saturation(), color.lightness(), color.whiteness(), and
  color.blackness() to use a quoted string.

v1.79.2

Compare Source

• Add a $space parameter to the suggested replacement for color.red(),
  color.green(), color.blue(), color.hue(), color.saturation(),
  color.lightness(), color.whiteness(), and color.blackness().

• Update deprecation warnings for the legacy JS API to include a link to
  relevant documentation.

v1.79.1

Compare Source

• No user-visible changes.

v1.79.0

Compare Source

• Breaking change: Passing a number with unit % to the $alpha parameter
  of color.change(), color.adjust(), change-color(), and adjust-color()
  is now interpreted as a percentage, instead of ignoring the unit. For example,
  color.change(red, $alpha: 50%) now returns rgb(255 0 0 / 0.5).

• Potentially breaking compatibility fix: Sass no longer rounds RGB channels
  to the nearest integer. This means that, for example, rgb(0 0 1) != rgb(0 0 0.6). This matches the latest version of the CSS spec and browser behavior.

• Potentially breaking compatibility fix: Passing large positive or negative
  values to color.adjust() can now cause a color's channels to go outside that
  color's gamut. In most cases this will currently be clipped by the browser and
  end up showing the same color as before, but once browsers implement gamut
  mapping it may produce a different result.

• Add support for CSS Color Level 4 [color spaces]. Each color value now tracks
  its color space along with the values of each channel in that color space.
  There are two general principles to keep in mind when dealing with new color
  spaces:

  1. With the exception of legacy color spaces (rgb, hsl, and hwb), colors
     will always be emitted in the color space they were defined in unless
     they're explicitly converted.

  2. The color.to-space() function is the only way to convert a color to
     another color space. Some built-in functions may do operations in a
     different color space, but they'll always convert back to the original space
     afterwards.

• rgb colors can now have non-integer channels and channels outside the normal
  gamut of 0-255. These colors are always emitted using the rgb() syntax so
  that modern browsers that are being displayed on wide-gamut devices can
  display the most accurate color possible.

• Add support for all the new color syntax defined in Color Level 4, including:

  • oklab(), oklch(), lab(), and lch() functions;
  • a top-level hwb() function that matches the space-separated CSS syntax;
  • and a color() function that supports the srgb, srgb-linear,
    display-p3, a98-rgb, prophoto-rgb, rec2020, xyz, xyz-d50, and
    xyz-d65 color spaces.

• Add new functions for working with color spaces:

  • color.to-space($color, $space) converts $color to the given $space. In
    most cases this conversion is lossless—the color may end up out-of-gamut for
    the destination color space, but browsers will generally display it as best
    they can regardless. However, the hsl and hwb spaces can't represent
    out-of-gamut colors and so will be clamped.

  • color.channel($color, $channel, $space: null) returns the value of the
    given $channel in $color, after converting it to $space if necessary.
    It should be used instead of the old channel-specific functions such as
    color.red() and color.hue().

  • `color.same(

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on the first day of january"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[webteam-app]

Demo starting at https://pythonoperatorframework-io-68.demos.haus

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.44%. Comparing base (4d2fec1) to head (04da057).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage   94.44%   94.44%           
=======================================
  Files           2        2           
  Lines          18       18           
=======================================
  Hits           17       17           
  Misses          1        1           

Flag	Coverage Δ
python	94.44% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.