Update all dependencies #192

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

`v10.4.20`

Fixed fit-content prefix for Firefox.

`v10.4.19`

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

`v10.4.18`

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

`v10.4.17`

Fixed user-select: contain prefixes.

postcss/postcss (postcss)

`v8.5.6`

Fixed ContainerWithChildren type discriminating (by @Goodwine).

`v8.5.5`

Fixed package.json→exports compatibility with some tools (by @JounQin).

`v8.5.4`

Fixed Parcel compatibility issue (by @git-sumitchaudhary).

`v8.5.3`

Added more details to Unknown word error (by @hiepxanh).
Fixed types (by @romainmenke).
Fixed docs (by @catnipan).

`v8.5.2`

Fixed end position of rules with semicolon (by @romainmenke).

`v8.5.1`

Fixed backwards compatibility for complex cases (by @romainmenke).

`v8.5.0`: 8.5 “Duke Alloces”

PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.

@romainmenke during his work on Stylelint added Input#document in additional to Input#css.

root.source.input.document //=> "<p>Hello</p>
                           //    <style>
                           //    p {
                           //      color: green;
                           //    }
                           //    </style>"
root.source.input.css      //=> "p {
                           //      color: green;
                           //    }"

Thanks to Sponsors

This release was possible thanks to our community.

If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:

Tidelift with a Spotify-like subscription model supporting all projects from your lock file.
Direct donations at GitHub Sponsors or Open Collective.

`v8.4.49`

Fixed custom syntax without source.offset (by @romainmenke).

`v8.4.48`

Fixed position calculation in error/warnings methods (by @romainmenke).

`v8.4.47`

Removed debug code.

`v8.4.46`

Fixed Cannot read properties of undefined (reading 'before').

`v8.4.45`

Removed unnecessary fix which could lead to infinite loop.

`v8.4.44`

Another way to fix markClean is not a function error.

`v8.4.43`

Fixed markClean is not a function error.

`v8.4.42`

Fixed CSS syntax error on long minified files (by @varpstar).

`v8.4.41`

Fixed types (by @nex3 and @querkmachine).
Cleaned up RegExps (by @bluwy).

`v8.4.40`

Moved to getter/setter in nodes types to help Sass team (by @nex3).

`v8.4.39`

Fixed CssSyntaxError types (by @romainmenke).

`v8.4.38`

Fixed endIndex: 0 in errors and warnings (by @romainmenke).

`v8.4.37`

Fixed original.column are not numbers error in another case.

`v8.4.36`

Fixed original.column are not numbers error on broken previous source map.

`v8.4.35`

Avoid ! in node.parent.nodes type.
Allow to pass undefined to node adding method to simplify types.

`v8.4.34`

Fixed AtRule#nodes type (by Tim Weißenfels).
Cleaned up code (by Dmitry Kirillov).

`v8.4.33`

Fixed NoWorkResult behavior difference with normal mode (by Romain Menke).
Fixed NoWorkResult usage conditions (by @ahmdammarr).

`v8.4.32`

Fixed postcss().process() types (by Andrew Ferreira).

prettier/prettier (prettier)

`v3.6.2`

Markdown: Add missing blank line around code block (#17675 by @fisker)

<!-- Input -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```

   1. Another
   2. List

<!-- Prettier 3.6.1 -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```
   1. Another
   2. List

<!-- Prettier 3.6.2 -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```

   1. Another
   2. List

`v3.6.1`

TypeScript: Allow const without initializer (#17650, #17654 by @fisker)

// Input
export const version: string;

// Prettier 3.6.0 (--parser=babel-ts)
SyntaxError: Unexpected token (1:21)
> 1 | export const version: string;
    |                     ^

// Prettier 3.6.0 (--parser=oxc-ts)
SyntaxError: Missing initializer in const declaration (1:14)
> 1 | export const version: string;
    |              ^^^^^^^^^^^^^^^

// Prettier 3.6.1
export const version: string;

Miscellaneous: Avoid closing files multiple times (#17665 by @43081j)

When reading a file to infer the interpreter from a shebang, we use the
n-readlines library to read the first line in order to get the shebang.

This library closes files when it reaches EOF, and we later try close the same
files again. We now close files only if n-readlines did not already close
them.

`v3.6.0`

`v3.5.3`

Flow: Fix missing parentheses in `ConditionalTypeAnnotation` (#17196 by @fisker)

// Input
type T<U> = 'a' | ('b' extends U ? 'c' : empty);
type T<U> = 'a' & ('b' extends U ? 'c' : empty);

// Prettier 3.5.2
type T<U> = "a" | "b" extends U ? "c" : empty;
type T<U> = "a" & "b" extends U ? "c" : empty;

// Prettier 3.5.3
type T<U> = "a" | ("b" extends U ? "c" : empty);
type T<U> = "a" & ("b" extends U ? "c" : empty);

`v3.5.2`

Remove `module-sync` condition (#17156 by @fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

`v3.5.1`

Fix CLI crash when cache for old version exists (#17100 by @sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#17101 by @remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

`v3.5.0`

`v3.4.2`

Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#16891 by @fisker)

// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

Fix non-idempotent formatting (#16899 by @seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

`v3.4.1`

Remove unnecessary parentheses around assignment in `v-on` (#16887 by @fisker)

<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

`v3.4.0`

`v3.3.3`

Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#16458 by @y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged template`)
class X {}

Support `@let` declaration syntax (#16474 by @sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

`v3.3.2`

Fix handlebars path expressions starts with `@` (#16358 by @Princeyadav05)

{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

`v3.3.1`

Preserve empty lines in front matter (#16347 by @fisker)

<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown

Preserve explicit language in front matter (#16348 by @fisker)

<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---

Avoid line breaks in import attributes (#16349 by @fisker)

// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

`v3.3.0`

`v3.2.5`

Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#15969 by @JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

Use `"json"` parser for `tsconfig.json` by default (#16012 by @sosukesuzuki)

In v3.2.0, we introduced "jsonc" parser which adds trailing comma by default.

When adding a new parser we also define how it will be used based on the linguist-languages data.

tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .prettierrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}

`v3.2.4`

prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "jsonc" }

`v3.2.3`

Throw errors for invalid code (#15881 by @fisker, @Josh-Cena, @auvred)

// Input
1++;

// Prettier 3.2.2
1++;

// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
    | ^

// Input
try {} catch (error = 1){}

// Prettier 3.2.2
try {
} catch (error) {}

// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
> 1 | try {} catch (error = 1){}
    |                       ^

Fix parser inference (#15927 by @fisker)

// Prettier 3.2.2
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "json" }

// Prettier 3.2.3
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "jsonc" }

`v3.2.2`

Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#15896 by @eelco)

For example this code would crash before:

<style {...spread}>{`.{}`}</style>

Fix formatting error on optional call expression and member chain (#15920 by @sosukesuzuki)

// Input
a(() => {}, c?.d());

// Prettier 3.2.1
TypeError: Cannot read properties of undefined (reading 'type')

// Prettier 3.2.2
a(() => {}, c?.d());

`v3.2.1`

Fix formatting error on member chain (#15915 by @sosukesuzuki)

// Input
test().test2().test2(thing?.something);

// Prettier 3.2.0
TypeError: Cannot read properties of undefined (reading 'type')

// Prettier 3.2.1
test().test2().test2(thing?.something);

`v3.2.0`

`v3.1.1`

Fix config file search (#15363 by @fisker)

Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake.

├─ .prettierrc
└─ test.js         (A directory)
  └─ .prettierrc

// Prettier 3.1.0
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/test.js/.prettierrc

// Prettier 3.1.1
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/.prettierrc

Skip explicitly passed symbolic links with `--no-error-on-unmatched-pattern` (#15533 by @sanmai-NL)

Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors.

In Prettier 3.1.1, you can use --no-error-on-unmatched-pattern to simply skip symbolic links.

Consistently use tabs in ternaries when `useTabs` is `true` (#15662 by @auvred)

// Input
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.0
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.1
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
		? ddddddddddddddd
		: eeeeeeeeeeeeeee
			? fffffffffffffff
			: gggggggggggggggg;

Improve config file search (#15663 by @fisker)

The Prettier config file search performance has been improved by more effective cache strategy.

Fix unstable and ugly formatting for comments in destructuring patterns (#15708 by @sosukesuzuki)

// Input
const {
  foo,
  // bar
  // baz
}: Foo = expr;

// Prettier 3.1.0
const {
  foo1,
} // bar
// baz
: Foo = expr;

// Prettier 3.1.0 second output
const {
  foo1, // bar
} // baz
: Foo = expr;

// Prettier 3.1.1
const {
  foo1,
  // bar
  // baz
}: Foo = expr;

Support "Import Attributes" (#15718 by @fisker)

TypeScript 5.3 supports the latest updates to the import attributes proposal.

import something from "./something.json" with { type: "json" };

Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#15750 by @ExplodingCabbage)

The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by @ds300. However, Prettier's documentation (including the CLI --help text) continued to claim otherwise, falsely. The documentation is now fixed.

Keep curly braces and `from` keyword in empty `import` statements (#15756 by @fisker)

// Input
import { } from 'foo';
import { /* comment */ } from 'bar';

// Prettier 3.1.0
import {} from "foo";
import /* comment */ "bar";

// Prettier 3.1.1
import {} from "foo";
import {} from /* comment */ "bar";

Keep empty import attributes and assertions (#15757 by @fisker)

// Input
import foo from "foo" with {};
import bar from "bar" assert {};

// Prettier 3.1.0
import foo from "foo";
import bar from "bar";

// Prettier 3.1.1
import foo from "foo" with {};
import bar from "bar" assert {};

`v3.1.0`

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

`v0.6.13`

Prevent Svelte files from breaking when there are duplicate classes (#359)
Ensure prettier-plugin-multiline-arrays and prettier-plugin-jsdoc work when used together with this plugin (#372)

`v0.6.12`

Add internal (unsupported) option to load Tailwind CSS using a different package name (#366)

`v0.6.11`

Support TypeScript configs and plugins when using v4 (#342)

`v0.6.10`

Add support for @zackad/prettier-plugin-twig (#327)
Drop support for @zackad/prettier-plugin-twig-melody (#327)
Update Prettier options types (#325)
Don't remove whitespace inside template literals in Svelte (#332)

`v0.6.9`

Introduce tailwindStylesheet option to replace tailwindEntryPoint (#330)

`v0.6.8`

Fix crash (#320)

`v0.6.7`

Improved performance with large Svelte, Liquid, and Angular files (#312)
Add support for @plugin and @config in v4 (#316)
Add support for Tailwind CSS v4.0.0-alpha.25 (#317)

`v0.6.6`

Add support for prettier-plugin-multiline-arrays (#299)
Add resolution cache for known plugins (#301)
Support Tailwind CSS v4.0.0-alpha.19 (#310)

`v0.6.5`

Only re-apply string escaping when necessary (#295)

`v0.6.4`

Export PluginOptions type (#292)

`v0.6.3`

Improve detection of string concatenation (#288)

`v0.6.2`

Changed

Only remove duplicate Tailwind classes (#277)
Make sure escapes in classes are preserved in string literals (#286)

`v0.6.1`

Prevent Svelte files from breaking when there are duplicate classes (#359)
Ensure prettier-plugin-multiline-arrays and prettier-plugin-jsdoc work when used together with this plugin (#372)

`v0.6.0`

Changed

Remove duplicate classes (#272)
Remove extra whitespace around classes (#272)

`v0.5.14`

Fixed

Fix detection of v4 projects on Windows (#265)

`v0.5.13`

Added

Add support for @zackad/prettier-plugin-twig-melody (#255)

`v0.5.12`

Added

Add support for prettier-plugin-sort-imports (#241)
Add support for Tailwind CSS v4.0 (#249)

`v0.5.11`

Changed

Bumped bundled version of Tailwind CSS to v3.4.1 (#240)

`v0.5.10`

Changed

Bumped bundled version of Tailwind CSS to v3.4 (#235)

`v0.5.9`

Fixed

Fixed location of embedded preflight CSS file (#231)

`v0.5.8`

Added

Re-enable support for prettier-plugin-marko (#229)

`v0.5.7`

Fixed

Fix sorting inside dynamic custom attributes (#225)

sass/dart-sass (sass)

`v1.89.2`

Embedded Host

Fixed a compilation error caused by an outdated buf dependency.

`v1.89.1`

No user-visible changes.

`v1.89.0`

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`

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`

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`

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

`v1.86.2`

No user-visible changes.

`v1.86.1`

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

`v1.86.0`

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`

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`

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`

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`

No user-visible changes.

`v1.83.3`

No user-visible changes.

`v1.83.2`

Properly display deprecation IDs for the JS Sass API.
Don't display deprecation IDs for user-defined deprecations.

`v1.83.1`

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`

Allow trailing commas in all argument and parameter lists.

`v1.82.0`

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`

No user-visible changes.

`v1.81.0`

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`

Embedded Host

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

`v1.80.6`

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`

Embedded Host

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

`v1.80.4`

No user-visible changes.

`v1.80.3`

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`

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

`v1.80.1`

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

`v1.80.0`

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

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`

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`

JS API

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

`v1.79.3`

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`

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`

No user-visible changes.

`v1.79.0`

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($color1, $color2) returns whether two colors represent the same
  color even across color spaces. It differs from $color1 == $color2 because
  == never consider colors in different (non-legacy) spaces as equal.
- color.is-in-gamut($color, $space: null) returns whether $color is
  in-gamut for its color space (or $space if it's passed).
- color.to-gamut($color, $space: null) returns $color constrained to its
  space's gamut (or to $space's gamut, if passed). This is generally not
  recommended since even older browsers will display out-of-gamut colors as
  best they can, but it may be necessary in some cases.
- color.space($color): Returns the name of $color's color space.
- color.is-legacy($color): Returns whether $color is in a legacy color
  space (rgb, hsl, or hwb).
- color.is-powerless($color, $channel, $space: null): Returns whether the
  given $channel of $color is powerless in $space (or its own color
  space). A channel is "powerless" if its value doesn't affect the way the
  color is displayed, such as hue for a color with 0 chroma.
- color.is-missing($color, $channel): Returns whether $channel's value is
  missing in $color. Missing channels can be explicitly specified using the
  special value none and can appear automatically when color.to-space()
  returns a color with a powerless channel. Missing channels are usually
  treated as 0, except when interpolating between two colors and in
  color.mix() where they're treated as the same value as the other color.
Update existing functions to support color spaces:
- hsl() and color.hwb() no longer forbid out-of-bounds values. Instead,
  they follow the CSS spec by clamping them to within the allowed range.
- color.change(), color.adjust(), and color.scale() now support all
  channels of all color spaces. However, if you want to modify a channel
  that's not in $color's own color space, you have to explicitly specify the
  space with the $space parameter. (For backwards-compatibility, this
  doesn't apply to legacy channels of legacy colors—for example, you can still
  adjust an rgb color's saturation without passing $space: hsl).
- color.mix() and color.invert() now support the standard CSS algorithm
  for interpolating between two colors (the same one that's used for gradients
  and animations). To use this, pass the color space to use for interpolation
  to the $method parameter. For polar color spaces like hsl and oklch,
  this parameter also allows you to specify how hue interpolation is handled.
- color.complement() now supports a $space parameter that indicates which
  color space should be used to take the complement.
- color.grayscale() now operates in the oklch space for non-legacy colors.
- color.ie-hex-str() now automatically converts its color to the rgb space
  and gamut-maps it so that it can continue to take colors from any color
  space.

The following functions are now deprecated, and uses should be replaced with
the new color-space-aware functions defined above:
- The color.red(), color.green(), color.blue(), color.hue(),
  color.saturation(), color.lightness(), color.whiteness(), and
  color.blackness() functions, as well as their global counterparts, should
  be replaced with calls to color.channel().
- The global adjust-hue(), saturate(), desaturate(), lighten(),
  darken(), transaprentize(), fade-out(), opacify(), and fade-in()
  functions should be replaced by color.adjust() or color.scale().
Add a global-builtin future deprecation, which can be opted-into with the
--future-deprecation flag or the futureDeprecations option in the JS or
Dart API. This emits warnings when any global built-in functions that are
now available in sass: modules are called. It will become active by default
in an upcoming release alongside the @import deprecation.

Dart API

Added a ColorSpace class which represents the various color spaces defined
in the CSS spec.
Added SassColor.space which returns a color's color space.
Added SassColor.channels and .channelsOrNull which returns a list
of channel values, with missing channels converted to 0 or exposed as null,
respectively.
Added SassColor.isLegacy, .isInGamut, .channel(), .isChannelMissing(),
.isChannelPowerless(), .toSpace(), .toGamut(), .changeChannels(), and
.interpolate() which do the same thing as the Sass functions of the
corresponding names.
SassColor.rgb() now allows out-of-bounds and non-integer arguments.
SassColor.hsl() and .hwb() now allow out-of-bounds arguments.
Added SassColor.hwb(), .srgb(), .srgbLinear(), .displayP3(),
.a98Rgb(), .prophotoRgb(), .rec2020(), .xyzD50(), .xyzD65(),
.lab(), .lch(), .oklab(), .oklch(), and .forSpace() constructors.
Deprecated SassColor.red, .green, .blue, .hue, .saturation,
.lightness, .whiteness, and .blackness in favor of
SassColor.channel().
Deprecated SassColor.changeRgb(), .changeHsl(), and .changeHwb() in
favor of SassColor.changeChannels().
Added SassNumber.convertValueToUnit() as a shorthand for
SassNumber.convertValue() with a single numerator.
Added InterpolationMethod and HueInterpolationMethod which collectively
represent the method to use to interpolate two colors.

JS API

While the legacy API has been deprecated since we released the modern API, we
now emit warnings when the legacy API is used to make sure users are aware
that it will be removed in Dart Sass 2.0.0. In the meantime, you can silence
these warnings by passing legacy-js-api in silenceDeprecations when using
the legacy API.
Modify SassColor to accept a new space option, with support for all the
new color spaces defined in Color Level 4.
Add SassColor.space which returns a color's color space.
Add SassColor.channels and .channelsOrNull which returns a list of channel
values, with missing channels converted to 0 or exposed as null, respectively.
Add SassColor.isLegacy, .isInGamut(), .channel(), .isChannelMissing(),
.isChannelPowerless(), .toSpace(), .toGamut(), .change(), and
.interpolate() which do the same thing as the Sass functions of the
corresponding names.
Deprecate SassColor.red, .green, .blue, .hue, .saturation,
.lightness, .whiteness, and .blackness in favor of
SassColor.channel().

Embedded Sass

Add Color SassScript value, with support for all the new color spaces
defined in Color Level 4.
Remove RgbColor, HslColor and HwbColor SassScript values.

`v1.78.0`

The meta.feature-exists function is now deprecated. This deprecation is
named feature-exists.
Fix a crash when using @at-root without any queries or children in the
indented syntax.

JS API

Backport the deprecation options (fatalDeprecations, futureDeprecations,
and silenceDeprecations) to the legacy JS API. The legacy JS API is itself
deprecated, and you should move off of it if possible, but this will allow
users of bundlers and other tools that are still using the legacy API to
still control deprecation warnings.
Fix a bug where accessing SourceSpan.url would crash when a relative URL was
passed to the Sass API.

Embedded Sass

Explicitly expose a sass executable from the sass-embedded npm package.
This was intended to be included in 1.63.0, but due to the way
platform-specific dependency executables are installed it did not work as
intended. Now users can run npx sass for local installs or just sass when
sass-embedded is installed globally.
Add linux-riscv64, linux-musl-riscv64, and android-riscv64 support for the
sass-embedded npm package.
Fix an edge case where the Dart VM could hang when shutting down when requests
were in flight.
Fix a race condition where the embedded host could fail to shut down if it was
closed around the same time a new compilation was started.
Fix a bug where parse-time deprecation warnings could not be controlled by
the deprecation options in some circumstances.

`v1.77.8`

No user-visible changes.

`v1.77.7`

Declarations that appear after nested rules are deprecated, because the
semantics Sass has historically used are different from the semantics
specified by CSS. In the future, Sass will adopt the standard CSS semantics.

See the Sass website for details.
Potentially breaking bug fix: // in certain places such as unknown
at-rule values was being preserved in the CSS output, leading to potentially
invalid CSS. It's now properly parsed as a silent comment and omitted from the
CSS output.

`v1.77.6`

Fix a few cases where comments and occasionally even whitespace wasn't allowed
between the end of Sass statements and the following semicolon.

`v1.77.5`

Fully trim redundant selectors generated by @extend.

`v1.77.4`

Embedded Sass

Support passing Version input for fatalDeprecations as string over
embedded protocol.
Fix a bug in the JS Embedded Host where Version could be incorrectly accepted
as input for silenceDeprecations and futureDeprecations in pure JS.

`v1.77.3`

Dart API

Deprecation.duplicateVariableFlags has been deprecated and replaced with
Deprecation.duplicateVarFlags to make it consistent with the
duplicate-var-flags name used on the command line and in the JS API.

`v1.77.2`

Don't emit deprecation warnings for functions and mixins beginning with __.
Allow user-defined functions whose names begin with _ and otherwise look
like vendor-prefixed functions with special CSS syntax.

Command-Line Interface

Properly handle the --silence-deprecation flag.
Handle the --fatal-deprecation and --future-deprecation flags for
--interactive mode.

`v1.77.1`

Fix a crash that could come up with importers in certain contexts.

`v1.77.0`

Don't throw errors for at-rules in keyframe blocks.

`v1.76.0`

Throw errors for misplaced statements in keyframe blocks.
Mixins and functions whose names begin with -- are now deprecated for
forwards-compatibility with the in-progress CSS functions and mixins spec.
This deprecation is named css-function-mixin.

`v1.75.0`

Fix a bug in which stylesheet canonicalization could be cached incorrectly
when custom importers or the Node.js package importer made decisions based on
the URL of the containing stylesheet.

JS API

Allow importer to be passed without url in StringOptionsWithImporter.

`v1.74.1`

No user-visible changes.

`v1.72.0`

Support adjacent /s without whitespace in between when parsing plain CSS
expressions.
Allow the Node.js pkg: importer to load Sass stylesheets for package.json
exports field entries without extensions.
When printing suggestions for variables, use underscores in variable names
when the original usage used underscores.

JavaScript API

Properly resolve pkg: imports with the Node.js package importer when
arguments are passed to the JavaScript process.

`v1.71.1`

Command-Line Interface

Ship the musl Linux release with the proper Dart executable.

JavaScript API

Export the NodePackageImporter class in ESM mode.
Allow NodePackageImporter to locate a default directory even when the
entrypoint is an ESM module.

Dart API

Make passing a null argument to NodePackageImporter() a static error rather
than just a runtime error.

Embedded Sass

In the JS Embedded Host, properly install the musl Linux embedded compiler
when running on musl Linux.

`v1.71.0`

For more information about pkg: importers, see the
announcement on the Sass blog.

Command-Line Interface

Add a --pkg-importer flag to enable built-in pkg: importers. Currently
this only supports the Node.js package resolution algorithm, via
--pkg-importer=node. For example, @use "pkg:bootstrap" will load
node_modules/bootstrap/scss/bootstrap.scss.

JavaScript API

Add a NodePackageImporter importer that can be passed to the importers
option. This loads files using the pkg: URL scheme according to the Node.js
package resolution algorithm. For example, @use "pkg:bootstrap" will load
node_modules/bootstrap/scss/bootstrap.scss. The constructor takes a single
optional argument, which indicates the base directory to use when locating
node_modules directories. It defaults to
path.dirname(require.main.filename).

Dart API

Add a NodePackageImporter importer that can be passed to the importers
option. This loads files using the pkg: URL scheme according to the Node.js
package resolution algorithm. For example, @use "pkg:bootstrap" will load
node_modules/bootstrap/scss/bootstrap.scss. The constructor takes a single
argument, which indicates the base directory to use when locating
node_modules directories.

`v1.70.0`

JavaScript API

Add a sass.initCompiler() function that returns a sass.Compiler object
which supports compile() and compileString() methods with the same API as
the global Sass object. On the Node.js embedded host, each sass.Compiler
object uses a single long-lived subprocess, making compiling multiple
stylesheets much more efficient.
Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler
object which supports compileAsync() and compileStringAsync() methods with
the same API as the global Sass object. On the Node.js embedded host, each
sass.AsynCompiler object uses a single long-lived subprocess, making
compiling multiple stylesheets much more efficient.

Embedded Sass

Support the CompileRequest.silent field. This allows compilations with no
logging to avoid unnecessary request/response cycles.
The Dart Sass embedded compiler now reports its name as "dart-sass" rather
than "Dart Sass", to match the JS API's info field.

`v1.69.7`

Embedded Sass

In the JS Embedded Host, properly install the x64 Dart Sass executable on
ARM64 Windows.

`v1.69.6`

Produce better output for numbers with complex units in meta.inspect() and
debugging messages.
Escape U+007F DELETE when serializing strings.
When generating CSS error messages to display in-browser, escape all code
points that aren't in the US-ASCII region. Previously only code points U+0100
LATIN CAPITAL LETTER A WITH MACRON were escaped.
Provide official releases for musl LibC and for Android.
Don't crash when running meta.apply() in asynchronous mode.

JS API

Fix a bug where certain exceptions could produce SourceSpans that didn't
follow the documented SourceSpan API.

`v1.69.5`

JS API

Compatibility with Node.js 21.0.0.

microsoft/TypeScript (typescript)

`v5.8.3`: TypeScript 5.8.3

For release notes, check out the release announcement.

Downloads are available on:

npm

`v5.8.2`: TypeScript 5.8

For release notes, check out the release announcement.

Downloads are available on:

npm

`v5.7.3`: TypeScript 5.7.3

For release notes, check out the release announcement.

Downloads are available on npm

`v5.7.2`: TypeScript 5.7