Update all dependencies #10

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

`v8.4.31`

Fixed \r parsing to fix CVE-2023-44270.

`v8.4.30`

Improved source map performance (by Romain Menke).

`v8.4.29`

Fixed Node#source.offset (by Ido Rosenthal).
Fixed docs (by Christian Oliff).

`v8.4.28`

Fixed Root.source.end for better source map (by Romain Menke).
Fixed Result.root types when process() has no parser.

`v8.4.27`

Fixed Container clone methods types.

`v8.4.26`

Fixed clone methods types.

`v8.4.25`

Improve stringify performance (by Romain Menke).
Fixed docs (by @vikaskaliramna07).

`v8.4.24`

Fixed Plugin types.

`v8.4.23`

Fixed warnings in TypeDoc.

`v8.4.22`

Fixed TypeScript support with node16 (by Remco Haszing).

`v8.4.21`

Fixed Input#error types (by Aleks Hudochenkov).

`v8.4.20`

Fixed source map generation for childless at-rules like @layer.

`v8.4.19`

Fixed whitespace preserving after AST transformations (by Romain Menke).

`v8.4.18`

Fixed an error on absolute: true with empty sourceContent (by Rene Haas).

`v8.4.17`

Fixed Node.before() unexpected behavior (by Romain Menke).
Added TOC to docs (by Mikhail Dedov).

`v8.4.16`

Fixed Root AST migration.

`v8.4.15`

Fixed AST normalization after using custom parser with old PostCSS AST.

`v8.4.14`

Print “old plugin API” warning only if plugin was used (by @zardoy).

`v8.4.13`

Fixed append() error after using .parent (by Jordan Pittman).

prettier/prettier (prettier)

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

`v3.0.3`

Add `preferUnplugged: true` to `package.json` (#15169 by @fisker and @so1ve)

Prettier v3 uses dynamic imports, user will need to unplug Prettier when Yarn's PnP mode is enabled, add preferUnplugged: true to package.json, so Yarn will install Prettier as unplug by default.

Support shared config that forbids `require()` (#15233 by @fisker)

If an external shared config package is used, and the package exports don't have require or default export.

In Prettier 3.0.2 Prettier fails when attempt to require() the package, and throws an error.

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in <packageName>/package.json

Allow argument of `require()` to break (#15256 by @fisker)

// Input
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

// Prettier 3.0.2
const plugin = require(global.STANDALONE
  ? path.join(__dirname, "../standalone.js")
  : path.join(__dirname, ".."));

// Prettier 3.0.3
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

Do not print trailing commas in arrow function type parameter lists in `ts` code blocks (#15286 by @sosukesuzuki)

<!-- Input -->
```ts
const foo = <T>() => {}
```

<!-- Prettier 3.0.2 -->
```ts
const foo = <T,>() => {}
```

<!-- Prettier 3.0.3 -->
```ts
const foo = <T>() => {}
```

Support TypeScript 5.2 `using` / `await using` declaration (#15321 by @sosukesuzuki)

Support for the upcoming Explicit Resource Management feature in ECMAScript. using / await using declaration

{
   using foo = new Foo();
   await using bar = new Bar();
}

`v3.0.2`

Break after `=` of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#15204 by @seiyab)

// Input
const { section, rubric, authors, tags } = await utils.upsertCommonData(mainData);

// Prettier 3.0.1
const { section, rubric, authors, tags } = await utils.upsertCommonData(
  mainData,
);

// Prettier 3.0.2
const { section, rubric, authors, tags } =
  await utils.upsertCommonData(mainData);

Do not add trailing comma for grouped scss comments (#15217 by @auvred)

/* Input */
$foo: (
	'property': (),
	// comment 1
	// comment 2
)

/* Prettier 3.0.1 */
$foo: (
  "property": (),
  // comment 1
  // comment 2,
);

/* Prettier 3.0.2 */
$foo: (
  "property": (),
  // comment 1
  // comment 2
);

Print `declare` and `export` keywords for nested namespace (#15249 by @sosukesuzuki)

// Input
declare namespace abc1.def {}
export namespace abc2.def {}

// Prettier 3.0.1
namespace abc1.def {}
namespace abc2.def {}

// Prettier 3.0.2
declare namespace abc1.def {}
export namespace abc2.def {}

`v3.0.1`

https://blog.vuejs.org/posts/vue-3-3#generic-components

Fix cursor positioning for a special case (#14812 by @fisker)

// <|> is the cursor position

/* Input */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>  } from "fs"

/* Prettier 3.0.0 */
// All messages are represented in JSON.
// So, the prettier.py <|>controls a subprocess which spawns "node {this_file}".
import {} from "fs"

/* Prettier 3.0.1 */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>} from "fs"

Fix plugins/estree.d.ts to make it a module (#15018 by @kingyue737)

Add export {} in plugins/estree.d.ts to fix the "File is not a module" error

Add parenthesis around leading multiline comment in return statement (#15037 by @auvred)

// Input
function fn() {
  return (
    /**
     * @&#8203;type {...}
     */ expression
  )
}

// Prettier 3.0.0
function fn() {
  return /**
   * @&#8203;type {...}
   */ expression;
}

// Prettier 3.0.1
function fn() {
  return (
    /**
     * @&#8203;type {...}
     */ expression
  );
}

Add support for Vue "Generic Components" (#15066 by @auvred)

<!-- Input -->
<script setup lang="ts" generic="T extends Type1 & Type2 & (Type3 | Type4), U extends string | number | boolean"></script>

<!-- Prettier 3.0.0 -->
<script
  setup
  lang="ts"
  generic="T extends Type1 & Type2 & (Type3 | Type4), U extends string | number | boolean"
></script>

<!-- Prettier 3.0.1 -->
<script
  setup
  lang="ts"
  generic="
    T extends Type1 & Type2 & (Type3 | Type4),
    U extends string | number | boolean
  "
></script>

Fix comments print in `IfStatement` (#15076 by @fisker)

function a(b) {
  if (b) return 1; // comment
  else return 2;
}

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

/* Prettier 3.0.1 */
function a(b) {
  if (b) return 1; // comment
  else return 2;
}

Add missing type definition for `printer.preprocess` (#15123 by @so1ve)

export interface Printer<T = any> {
  // ...
+ preprocess?:
+   | ((ast: T, options: ParserOptions<T>) => T | Promise<T>)
+   | undefined;
}

Add missing `getVisitorKeys` method type definition for `Printer` (#15125 by @auvred)

const printer: Printer = {
  print: () => [],
  getVisitorKeys(node, nonTraversableKeys) {
    return ["body"];
  },
};

Add typing to support `readonly` array properties of AST Node (#15127 by @auvred)

// Input
interface TestNode {
  readonlyArray: readonly string[];
}

declare const path: AstPath<TestNode>;

path.map(() => "", "readonlyArray");

// Prettier 3.0.0
interface TestNode {
  readonlyArray: readonly string[];
}

declare const path: AstPath<TestNode>;

path.map(() => "", "readonlyArray");
//                  ^ Argument of type '"readonlyArray"' is not assignable to parameter of type '"regularArray"'. ts(2345)

// Prettier 3.0.1
interface TestNode {
  readonlyArray: readonly string[];
}

declare const path: AstPath<TestNode>;

path.map(() => "", "readonlyArray");

Add space before unary minus followed by a function call (#15129 by @pamelalozano)

// Input
div {
  margin: - func();
}

// Prettier 3.0.0
div {
  margin: -func();
}

// Prettier 3.0.1
div {
  margin: - func();
}

`v3.0.0`

`v2.8.8`

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`

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

// Input
class A {
  @&#8203;decorator()
  get foo () {}
  
  @&#8203;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 |   @&#8203;decorator()
    |   ^^^^^^^^^^^^
  6 |   set foo (value) {}
  7 | }

// Prettier 2.8.7
class A {
  @&#8203;decorator()
  get foo() {}

  @&#8203;decorator()
  set foo(value) {}
}

`v2.8.6`

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

// Input
class A {
  @&#8203;decorator()
  #privateMethod () {}
}

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

// Prettier 2.8.6
class A {
  @&#8203;decorator()
  #privateMethod() {}
}

`v2.8.5`

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 {
  @&#8203;(myDecoratorArray[0])
  greet() {}
}

// Prettier 2.8.4
class Person {
  @&#8203;myDecoratorArray[0]
  greet() {}
}

// Prettier 2.8.5
class Person {
  @&#8203;(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`

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`

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`

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
@&#8203;variable: {
  field: something;
};

// Prettier 2.8.1
@&#8203;variable: {
  field: something;
}; ;

// Prettier 2.8.2
@&#8203;variable: {
  field: something;
};

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

// Input
.unary_minus_single {
  margin: -(@&#8203;a);
}

.unary_minus_multi {
  margin: 0 -(@&#8203;a);
}

.binary_minus {
  margin: 0 - (@&#8203;a);
}

// Prettier 2.8.1
.unary_minus_single {
  margin: - (@&#8203;a);
}

.unary_minus_multi {
  margin: 0 - (@&#8203;a);
}

.binary_minus {
  margin: 0 - (@&#8203;a);
}

// Prettier 2.8.2
.unary_minus_single {
  margin: -(@&#8203;a);
}

.unary_minus_multi {
  margin: 0 -(@&#8203;a);
}

.binary_minus {
  margin: 0 - (@&#8203;a);
}

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

// Input
@&#8203;var: {
  preserveCase: 0;
};

// Prettier 2.8.1
@&#8203;var: {
  preservecase: 0;
};

// Prettier 2.8.2
@&#8203;var: {
  preserveCase: 0;
};

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

// Input
class A {
  @&#8203;dec()
  // comment
  accessor b;
}

// Prettier 2.8.1
class A {
  @&#8203;dec()
  accessor // comment
  b;
}

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

// Prettier 2.8.2
class A {
  @&#8203;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: @&#8203;colors[@&#8203;white];
}

// Prettier 2.8.1
a {
  color: @&#8203;colors[ @&#8203;white];
}

// Prettier 2.8.2
<Same as input>

`v2.8.1`

Fix SCSS map in arguments (#9184 by @agamkrbit)

// Input
$display-breakpoints: map-deep-merge(
  (
    "print-only": "only print",
    "screen-only": "only screen",
    "xs-only": "only screen and (max-width: #{map-get($grid-breakpoints, "sm")-1})",
  ),
  $display-breakpoints
);

// Prettier 2.8.0
$display-breakpoints: map-deep-merge(
  (
    "print-only": "only print",
    "screen-only": "only screen",
    "xs-only": "only screen and (max-width: #{map-get($grid-breakpoints, " sm
      ")-1})",
  ),
  $display-breakpoints
);

// Prettier 2.8.1
$display-breakpoints: map-deep-merge(
  (
    "print-only": "only print",
    "screen-only": "only screen",
    "xs-only": "only screen and (max-width: #{map-get($grid-breakpoints, "sm")-1})",
  ),
  $display-breakpoints
);

Support auto accessors syntax (#13919 by @sosukesuzuki)

Support for Auto Accessors Syntax landed in TypeScript 4.9.

(Doesn't work well with babel-ts parser)

class Foo {
  accessor foo: number = 3;
}

`v2.8.0`

`v2.7.1`

Keep useful empty lines in description (#13013 by @chimurai)

`v2.7.0`

"""
First line
Second Line
"""
type Person {
name: String
}

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

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

Added

Add new tailwindPreserveDuplicates option to disable removal of duplicate classes (#276)

Fixed

Improve handling of whitespace removal when concatenating strings (#276)
Fix a bug where Angular expressions may produce invalid code after sorting (#276)
Disabled whitespace and duplicate class removal for Liquid and Svelte (#276)

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

`v0.5.6`

Fixed

Fix sorting inside {{ … }} expressions when using @shopify/prettier-plugin-liquid v1.3+ (#222)

`v0.5.5`

Fixed

Sort classes inside className in Astro (#215)
Support member access on function calls (#218)

`v0.5.4`

Fixed

Type tailwindFunctions and tailwindAttributes as optional (#206)
Don’t break @apply … #{'!important'} sorting in SCSS (#212)

`v0.5.3`

Fixed

Fix CJS __dirname interop on Windows (#204)

`v0.5.2`

Fixed

Fix intertop with bundled CJS dependencies (#199)

`v0.5.1`

Fixed

Fix detection of v4 projects on Windows (#265)

`v0.5.0`

Added

Sort expressions in Astro's class:list attribute (#192)
Re-enabled support for plugins when using Prettier v3+ (#195)

`v0.4.1`

Fixed

Don't move partial classes inside Twig attributes (#184)

`v0.4.0`

Added

Export types for Prettier config (#162)
Add Prettier v3 support (#179)

Fixed

Don't move partial classes inside Liquid script attributes (#164)
Do not split classes by non-ASCII whitespace (#166)
Match tagged template literals with tag expressions (#169)

`v0.3.0`

Added

Added support for prettier-plugin-marko (#151)
Allow sorting of custom attributes, functions, and tagged template literals (#155)

Fixed

Speed up formatting (#153)
Fix plugin compatibility when loaded with require (#159)

`v0.2.8`

Changed

Remove support for @prettier/plugin-php (#152)

`v0.2.7`

Fixed

Don't break liquid tags inside attributes when sorting classes (#143)

`v0.2.6`

Added

Support ESM and TS config files (#137)

Fixed

Load tailwindcss modules from nearest instance only (#139)

`v0.2.5`

Fixed

Fix class sorting in capture liquid tag (#131)

`v0.2.4`

Fixed

Sort class attribute on components and custom elements in Astro (#129)

`v0.2.3`

Fixed

Don't sort classes in Glimmer concat helper (#119)
Add support for @ianvs/prettier-plugin-sort-imports (#122)

`v0.2.2`

Fixed

Add prettier plugins to peer dependencies (#114)
Traverse await expression blocks in Svelte (#118)

`v0.2.1`

Fixed

Fix support for latest Shopify Liquid plugin (#109)

`v0.2.0`

Changed

Don't bundle prettier-plugin-svelte (#101)

Added

Improve compatibility with other Prettier plugins (#101, #102)

sass/dart-sass (sass)

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

`v1.69.4`

No user-visible changes.

`v1.69.3`

Embedded Sass

Fix TypeScript type locations in package.json.

`v1.69.2`

JS API

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

`v1.69.1`

No user-visible changes.

`v1.69.0`

Add a meta.get-mixin() function that returns a mixin as a first-class Sass
value.
Add a meta.apply() mixin that includes a mixin value.
Add a meta.module-mixins() function which returns a map from mixin names in
a module to the first-class mixins that belong to those names.
Add a meta.accepts-content() function which returns whether or not a mixin
value can take a content block.
Add support for the relative color syntax from CSS Color 5. This syntax
cannot be used to create Sass color values. It is always emitted as-is in the
CSS output.

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`

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`

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`

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`

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`

Update abs-percent deprecatedIn version to 1.65.0.

`v1.65.0`

All functions defined in CSS Values and Units 4 are now parsed as calculation
objects: round(), mod(), rem(), sin(), cos(), tan(), asin(),
acos(), atan(), atan2(), pow(), sqrt(), hypot(), log(), exp(),
abs(), 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`

No user-visible changes.

`v1.64.1`

Embedded Sass

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

`v1.64.0`

Comments that appear before or between @use and @forward rules are now
emitted in source order as much as possible, instead of always being emitted
after the CSS of all module dependencies.
Fix a bug where an interpolation in a custom property name crashed if the file
was loaded by a @use nested in an @import.

JavaScript API

Add a new SassCalculation type that represents the calculation objects added
in Dart Sass 1.40.0.
Add Value.assertCalculation(), which returns the value if it's 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`

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`

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`

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`

JavaScript API

Fix loading Sass as an ECMAScript module on Node.js.

`v1.63.2`

No user-visible changes.

`v1.63.1`

No user-visible changes.

`v1.63.0`

JavaScript API

Dart Sass's JS API now supports running in the browser. Further details and
instructions for use are in the README.

Embedded Sass

The Dart Sass embedded compiler is now included as part of the primary Dart
Sass distribution, rather than a separate executable. To use the embedded
compiler, just run sass --embedded from any Sass executable (other than the
pure JS executable).

The Node.js embedded host will still be distributed as the sass-embedded
package on npm. The only change is that it will now provide direct access to 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`

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

`v1.62.0`

Deprecate the use of multiple !global or !default flags on the same
variable. This deprecation is 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`

Potentially breaking change: Drop support for End-of-Life Node.js 12.
Fix remaining cases for the performance regression introduced in 1.59.0.

Embedded Sass

The JS embedded host now loads files from the working directory when using the
legacy API.

`v1.60.0`

Add support for the pi, e, infinity, -infinity, 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`

Fix a performance regression introduced in 1.59.0.
The NPM release of 1.59.0 dropped support for Node 12 without actually
indicating so in its pubspec. This release temporarily adds back support so
that the latest Sass version that declares it supports Node 12 actually does
so. However, Node 12 is now end-of-life, so we will drop support for it
properly in an upcoming release.

`v1.59.2`

No user-visible changes.

`v1.59.1`

No user-visible changes.

`v1.59.0`

Command Line Interface

Added a new --fatal-deprecation flag that lets you treat a deprecation
warning as an error. You can pass an individual deprecation ID
(e.g. slash-div) or you can pass a Dart Sass version to treat all
deprecations initially emitted in that version or earlier as errors.
New --future-deprecation flag that lets you opt into warning for use of
certain features that will be deprecated in the future. At the moment, the
only option is --future-deprecation=import, which will emit warnings for
Sass @import rules, which are not yet deprecated, but will be in the future.

Dart API

New Deprecation enum, which contains the different current and future
deprecations used by the new CLI flags.
The compile methods now take in fatalDeprecations and futureDeprecations
parameters, which work similarly to the CLI flags.

`v1.58.3`

No user-visible changes.

`v1.58.2`

Command Line Interface

Add a timestamp to messages printed in --watch mode.
Print better calc()-based suggestions for /-as-division expression that
contain calculation-incompatible constructs like unary minus.

`v1.58.1`

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

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`

No user-visible changes.

`v1.57.0`

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`

Embedded Sass

The embedded compiler now supports version 1.2.0 of the embedded
protocol.

`v1.56.1`

Embedded Sass

Importer results now validate that contents is actually a string and whether
sourceMapUrl is an absolute URL.

`v1.56.0`

Potentially breaking change: To match the CSS spec, SassScript expressions
beginning with not or ( are no longer supported at the beginning of
parenthesized sections of media queries. For example,
```
@&#8203;media (width >= 500px) and (not (grid))
```
will now be emitted unchanged, instead of producing
```
@&#8203;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`

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`

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

`v1.54.8`

No user-visible changes.

`v1.54.7`

Add support for 32-bit ARM releases on Linux.

`v1.54.6`

Fix a bug where a @media query could be incorrectly omitted from a
stylesheet if it had multiple levels of nested @media queries within it
and the inner queries were mergeable but the outer query was not.

`v1.54.5`

Properly consider a ~ c to be a superselector 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`

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

`v1.54.3`

Release a native ARM64 executable for Mac OS.

`v1.54.2`

No user-visible changes.

`v1.54.1`

When unifying selectors for @extend and selector.unify(), ensure that
:root, :scope, :host, and :host-context only appear at the beginning
of complex selectors.

`v1.54.0`

Deprecate selectors with leading or trailing combinators, or with multiple
combinators in a row. If they're included in style rules after nesting is
resolved, Sass will now produce a deprecation warning and, in most cases, omit
the selector. Leading and trailing combinators can still be freely used for
nesting purposes.

See https://sass-lang.com/d/bogus-combinators for more details.
Add partial support for new media query syntax from Media Queries Level 4. The
only exception are logical operations nested within parentheses, as these were
previously interpreted differently as SassScript expressions.

A parenthesized media condition that begins with not or an opening
parenthesis now produces a deprecation warning. In a future release, these
will be interpreted as plain CSS instead.
Deprecate passing non-deg units 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`

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`

Fix crash when trailing loud comments (/* ... */) appear twice in a row
across two different imports which themselves imported the same file each.

`v1.52.2`

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

`v1.52.1`

Command Line Interface

Fix a bug where --watch mode would close immediately in TTY mode. This was
caused by our change to close --watch when stdin was closed outside of TTY
mode, which has been reverted for now while we work on a fix.

`v1.52.0`

Add support for arbitrary modifiers at the end of plain CSS imports, in
addition to the existing supports() and media queries. Sass now allows any
sequence of identifiers of functions after the URL of an import for forwards
compatibility with future additions to the CSS spec.
Fix an issue where source locations tracked through variable references could
potentially become incorrect.
Fix a bug where a loud comment in the source can break the source map when
embedding the sources, when using the command-line interface or the legacy JS
API.

JS API

SassNumber.assertUnit() and SassNumber.assertNoUnits() now correctly
return the number called on when it passes the assertion.

`v1.51.0`

Potentially breaking change: Change the order of maps returned by
map.deep-merge() to match those returned 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.

tailwindlabs/tailwindcss (tailwindcss)

`v3.4.15`

Bump versions for security vulnerabilities (#14697)
Ensure the TypeScript types for the boxShadow theme configuration allows arrays (#14856)
Set fallback for opacity variables to ensure setting colors with the selection:* variant works in Chrome 131 (#15003)

`v3.4.14`

Fixed

Don't set display: none on elements that use hidden="until-found" (#14625)

`v3.4.13`

Fixed

Improve source glob verification performance (#14481)

`v3.4.12`

Fixed

Ensure using @apply with utilities that use @defaults works with rules defined in the base layer when using optimizeUniversalDefaults (#14427)

`v3.4.11`

Fixed

Allow anchor-size(…) in arbitrary values (#14393)

`v3.4.10`

Fixed

Bump versions of plugins in the Standalone CLI (#14185)

`v3.4.9`

Fixed

No longer warns when broad glob patterns are detecting vendor folders

`v3.4.8`

Fixed

Fix minification when using nested CSS (#14105)
Warn when broad glob patterns are used in the content configuration (#14140)

`v3.4.7`

Fixed

Fix class detection in Slim templates with attached attributes and ID (#14019)
Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#14037)

`v3.4.6`

Fixed

Fix detection of some utilities in Slim/Pug templates (#14006)

Changed

Loosen :is() wrapping rules when using an important selector (#13900)

`v3.4.5`

Fixed

Disable automatic var() injection for anchor properties (#13826)
Use no value instead of blur(0px) for backdrop-blur-none and blur-none utilities (#13830)
Add .mts and .cts config file detection (#13940)
Don't generate utilities like px-1 unnecessarily when using utilities like px-1.5 (#13959)
Always generate -webkit-backdrop-filter for backdrop-* utilities (#13997)

`v3.4.4`

Fixed

Make it possible to use multiple <alpha-value> placeholders in a single color definition (#13740)
Don't prefix classes in arbitrary values of has-*, group-has-*, and peer-has-* variants (#13770)
Support negative values for {col,row}-{start,end} utilities (#13781)
Update embedded browserslist database (#13792)

`v3.4.3`

Fixed

Revert changes to glob handling (#13384)

`v3.4.2`

Fixed

Ensure max specificity of 0,0,1 for button and input Preflight rules (#12735)
Improve glob handling for folders with (, ), [ or ] in the file path (#12715)
Split :has rules when using experimental.optimizeUniversalDefaults (#12736)
Sort arbitrary properties alphabetically across multiple class lists (#12911)
Add mix-blend-plus-darker utility (#12923)
Ensure dashes are allowed in variant modifiers (#13303)
Fix crash showing completions in Intellisense when using a custom separator (#13306)
Transpile import.meta.url in config files (#13322)
Reset letter spacing for form elements (#13150)
Fix missing xx-large and remove double x-large absolute size (#13324)
Don't error when encountering nested CSS unless trying to @apply a class that uses nesting (#13325)
Ensure that arbitrary properties respect important configuration (#13353)
Change dark mode selector so @apply works correctly with pseudo elements (#13379)

`v3.4.1`

Fixed

Don't remove keyframe stops when using important utilities (#12639)
Don't add spaces to gradients and grid track names when followed by calc() (#12704)
Restore old behavior for class dark mode strategy (#12717)

Added

Add new selector and variant strategies for dark mode (#12717)

Changed

Support rtl and ltr variants on same element as dir attribute (#12717)

`v3.4.0`

Tailwind CSS v3.4 has arrived! Check out the announcement post for a guided tour through all of the highlights.

Added

Add svh, lvh, and dvh values to default height/min-height/max-height theme (#11317)
Add has-* variants for :has(...) pseudo-class (#11318)
Add text-wrap utilities including text-balance and text-pretty (#11320, #12031)
Extend default opacity scale to include all steps of 5 (#11832)
Update Preflight html styles to include shadow DOM :host pseudo-class (#11200)
Increase default values for grid-rows-* utilities from 1–6 to 1–12 (#12180)
Add size-* utilities (#12287)
Add utilities for CSS subgrid (#12298)
Add spacing scale to min-w-*, min-h-*, and max-w-* utilities (#12300)
Add forced-color-adjust utilities (#11931)
Add forced-colors variant (#11694, #12582)
Add appearance-auto utility (#12404)
Add logical property values for float and clear utilities (#12480)
Add * variant for targeting direct children (#12551)

Changed

Simplify the sans font-family stack (#11748)
Disable the tap highlight overlay on iOS (#12299)
Improve relative precedence of rtl, ltr, forced-colors, and dark variants (#12584)

`v3.3.7`

Fixed

Fix support for container query utilities with arbitrary values (#12534)
Fix custom config loading in Standalone CLI (#12616)

`v3.3.6`

Fixed

Don’t add spaces to negative numbers following a comma (#12324)
Don't emit @config in CSS when watching via the CLI (#12327)
Improve types for resolveConfig (#12272)
Ensure configured font-feature-settings for mono are included in Preflight (#12342)
Improve candidate detection in minified JS arrays (without spaces) (#12396)
Don't crash when given applying a variant to a negated version of a simple utility (#12514)
Fix support for slashes in arbitrary modifiers (#12515)
Fix source maps of variant utilities that come from an @layer rule (#12508)
Fix loading of built-in plugins when using an ESM or TypeScript config with the Standalone CLI (#12506)

`v3.3.5`

Fixed

Fix incorrect spaces around - in calc() expression (#12283)

`v3.3.4`

Fixed

Improve normalisation of calc()-like functions (#11686)
Skip calc() normalisation in nested theme() calls (#11705)
Fix incorrectly generated CSS when using square brackets inside arbitrary properties (#11709)
Make content optional for presets in TypeScript types (#11730)
Handle variable colors that have variable fallback values (#12049)
Batch reading content files to prevent too many open files error (#12079)
Skip over classes inside :not(…) when nested in an at-rule (#12105)
Update types to work with Node16 module resolution (#12097)
Don’t crash when important and parent selectors are equal in @apply (#12112)
Eliminate irrelevant rules when applying variants (#12113)
Improve RegEx parser, reduce possibilities as the key for arbitrary properties (#12121)
Fix sorting of utilities that share multiple candidates (#12173)
Ensure variants with arbitrary values and a modifier are correctly matched in the RegEx based parser (#12179)
Fix crash when watching renamed files on FreeBSD (#12193)
Allow plugins from a parent document to be used in an iframe (#12208)
Add types for tailwindcss/nesting (#12269)
Bump jiti, fast-glob, and browserlist dependencies (#11550)
Improve automatic var injection for properties that accept a <dashed-ident> (#12236)

`v3.3.3`

Fixed

Fix issue where some pseudo-element variants generated the wrong selector (#10943, #10962, #11111)
Make font settings propagate into buttons, inputs, etc. (#10940)
Fix parsing of theme() inside calc() when there are no spaces around operators (#11157)
Ensure repeating-conic-gradient is detected as an image (#11180)
Move unknown pseudo-elements outside of :is by default (#11345)
Escape animation names when prefixes contain special characters (#11470)
Don't prefix arbitrary classes in group and peer variants (#11454)
Sort classes using position of first matching rule (#11504)
Allow variant to be an at-rule without a prelude (#11589)
Make PostCSS plugin async to improve performance (#11548)
Don’t error when a config file is missing (f97759f)

Added

Add aria-busy utility (#10966)

Changed

Reset padding for <dialog> elements in preflight (#11069)

`v3.3.2`

Fixed

Don’t move unknown pseudo-elements to the end of selectors (#10943, #10962)
Inherit gradient stop positions when using variants (#11002)
Honor default to position of gradient when using implicit transparent colors (#11002)
Ensure @tailwindcss/oxide doesn't leak in the stable engine (#10988)
Ensure multiple theme(spacing[5]) calls with bracket notation in arbitrary properties work (#11039)
Normalize arbitrary modifiers (#11057)

Changed

Drop support for Node.js v12 (#11089)

`v3.3.1`

Fixed

Fix edge case bug when loading a TypeScript config file with webpack (#10898)
Fix variant, @apply, and important selectors when using :is() or :has() with pseudo-elements (#10903)
Fix safelist config types (#10901)
Fix build errors caused by @tailwindcss/line-clamp warning (#10915, #10919)
Fix "process is not defined" error (#10919)

`v3.3.0`

Tailwind CSS v3.3 is here! Check out the announcement post for a deep dive into all of the cool new stuff.

Added

Support ESM and TypeScript config files (#10785)
Extend default color palette with new 950 shades (#10879)
Add line-height modifier support to font-size utilities (#9875)
Add support for using variables as arbitrary values without var(...) (#9880, #9962)
Add logical properties support for inline direction (#10166)
Add hyphens utilities (#10071)
Add from-{position}, via-{position} and to-{position} utilities (#10886)
Add list-style-image utilities (#10817)
Add caption-side utilities (#10470)
Add line-clamp utilities from @tailwindcss/line-clamp to core (#10768, #10876, #10862)
Add delay-0 and duration-0 utilities (#10294)
Add justify-normal and justify-stretch utilities (#10560)
Add content-normal and content-stretch utilities (#10645)
Add whitespace-break-spaces utility (#10729)
Add support for configuring default font-variation-settings for a font-family (#10034, #10515)

Fixed

Disallow using multiple selectors in arbitrary variants (#10655)
Sort class lists deterministically for Prettier plugin (#10672)
Ensure CLI builds have a non-zero exit code on failure (#10703)
Ensure module dependencies for value null, is an empty Set (#10877)
Fix format assumption when resolving module dependencies (#10878)

Changed

Mark rtl and ltr variants as stable and remove warnings (#10764)
Use inset instead of top, right, bottom, and left properties (#10765)
Make dark and rtl/ltr variants insensitive to DOM order (#10766)
Use :is to make important selector option insensitive to DOM order (#10835)

`v3.2.7`

Fixed

Fix use of :where(.btn) when matching !btn (#10601)
Revert including outline-color in transition and transition-colors by default (#10604)

`v3.2.6`

Fixed

Fix installation failing with yarn and pnpm by dropping oxide-api-shim (add1636)

`v3.2.5`

Added

Add standalone CLI build for 64-bit Windows on ARM (node16-win-arm64) (#10001)

Fixed

Cleanup unused variantOrder (#9829)
Fix foo-[abc]/[def] not being handled correctly (#9866)
Add container queries plugin to standalone CLI (#9865)
Support renaming of output files by PostCSS plugins in CLI (#9944)
Improve return value of resolveConfig, unwrap ResolvableTo (#9972)
Clip unbalanced brackets in arbitrary values (#9973)
Don’t reorder webkit scrollbar pseudo elements (#9991)
Deterministic sorting of arbitrary variants (#10016)
Add data key to theme types (#10023)
Prevent invalid arbitrary variant selectors from failing the build (#10059)
Properly handle subtraction followed by a variable (#10074)
Fix missing string[] in the theme.dropShadow types (#10072)
Update list of length units (#10100)
Fix not matching arbitrary properties when closely followed by square brackets (#10212)
Allow direct nesting in root or @layer nodes (#10229)
Don't prefix classes in arbitrary variants (#10214)
Fix perf regression when checking for changed content (#10234)
Fix missing blocklist member in the Config type (#10239)
Escape group names in selectors (#10276)
Consider earlier variants before sorting functions (#10288)
Allow variants with slashes (#10336)
Ensure generated CSS is always sorted in the same order for a given set of templates (#10382)
Handle variants when the same class appears multiple times in a selector (#10397)
Handle group/peer variants with quoted strings (#10400)
Parse alpha value from rgba/hsla colors when using variables (#10429)
Sort by layer inside variants layer (#10505)
Add --watch=always option to prevent exit when stdin closes (#9966)

Changed

Alphabetize theme keys in default config (#9953)
Update esbuild to v17 (#10368)
Include outline-color in transition and transition-colors utilities (#10385)

`v3.2.4`

Added

Add blocklist option to prevent generating unwanted CSS (#9812)

Fixed

Fix watching of files on Linux when renames are involved (#9796)
Make sure errors are always displayed when watching for changes (#9810)

`v3.2.3`

Fixed

Fixed use of raw content in the CLI (#9773)
Pick up changes from files that are both context and content deps (#9787)
Sort pseudo-elements ONLY after classes when using variants and @apply (#9765)
Support important utilities in the safelist (pattern must include a !) (#9791)

`v3.2.2`

Fixed

Escape special characters in resolved content base paths (#9650)
Don't reuse container for array returning variant functions (#9644)
Exclude non-relevant selectors when generating rules with the important modifier (#9677)
Fix merging of arrays during config resolution (#9706)
Ensure configured font-feature-settings are included in Preflight (#9707)
Fix fractional values not being parsed properly inside arbitrary properties (#9705)
Fix incorrect selectors when using @apply in selectors with combinators and pseudos (#9722)
Fix cannot read properties of undefined (reading 'modifier') (#9656, aa979d6)

`v3.2.1`

Fixed

Fix missing supports in types (#9616)
Fix missing PostCSS dependencies in the CLI (#9617)
Ensure micromatch is a proper CLI dependency (#9620)
Ensure modifier values exist when using a modifiers object for matchVariant (ba6551d)

`v3.2.0`

We just released Tailwind CSS v3.2! Read the announcement post for more details about the most exciting new features.

Added

Add new @config directive (#9405)
Add new relative: true option to resolve content paths relative to the config file (#9396)
Add new supports-* variant (#9453)
Add new min-* and max-* variants (#9558)
Add new aria-* variants (#9557, #9588)
Add new data-* variants (#9559, #9588)
Add new break-keep utility for word-break: keep-all (#9393)
Add new collapse utility for visibility: collapse (#9181)
Add new fill-none utility for fill: none (#9403)
Add new stroke-none utility for stroke: none (#9403)
Add new place-content-baseline utility for place-content: baseline (#9498)
Add new place-items-baseline utility for place-items: baseline (#9507)
Add new content-baseline utility for align-content: baseline (#9507)
Add support for configuring default font-feature-settings for a font family (#9039)
Add standalone CLI build for 32-bit Linux on ARM (node16-linux-armv7) (#9084)
Add future flag to disable color opacity utility plugins (#9088)
Add negative value support for outline-offset (#9136)
Add support for modifiers to matchUtilities (#9541)
Allow negating utilities using min/max/clamp (#9237)
Implement fallback plugins when there is ambiguity between plugins when using arbitrary values (#9376)
Support sort function in matchVariant (#9423)
Upgrade to postcss-nested v6.0 (#9546)

Fixed

Use absolute paths when resolving changed files for resilience against working directory changes (#9032)
Fix ring color utility generation when using respectDefaultRingColorOpacity (#9070)
Sort tags before classes when @apply-ing a selector with joined classes (#9107)
Remove invalid outline-hidden utility (#9147)
Honor the hidden attribute on elements in preflight (#9174)
Don't stop watching atomically renamed files (#9173, #9215)
Fix duplicate utilities issue causing memory leaks (#9208)
Fix fontFamily config TypeScript types (#9214)
Handle variants on complex selector utilities (#9262)
Fix shared config mutation issue (#9294)
Fix ordering of parallel variants (#9282)
Handle variants in utility selectors using :where() and :has() (#9309)
Improve data type analysis for arbitrary values (#9320)
Don't emit generated utilities with invalid uses of theme functions (#9319)
Revert change that only listened for stdin close on TTYs (#9331)
Ignore unset values (like null or undefined) when resolving the classList for intellisense (#9385)
Improve type checking for formal syntax (#9349, #9448)
Fix incorrect required content key in custom plugin configs (#9502, #9545)
Fix content path detection on Windows (#9569)
Ensure --content is used in the CLI when passed (#9587)

`v3.1.8`

Fixed

Don’t prefix classes within reused arbitrary variants (#8992)
Fix usage of alpha values inside single-named colors that are functions (#9008)
Fix @apply of user utilities when negative and non-negative versions both exist (#9027)

`v3.1.7`

Fixed

Don't rewrite source maps for @layer rules (#8971)

Added

Added types for resolveConfig (#8924)

`v3.1.6`

Fixed

Fix usage on Node 12.x (b4e637e)
Handle theme keys with slashes when using theme() in CSS (#8831)

`v3.1.5`

Added

Support configuring a default font-weight for each font size utility (#8763)
Add support for alpha values in safe list (#8774)

Fixed

Improve types to support fallback values in the CSS-in-JS syntax used in plugin APIs (#8762)
Support including tailwindcss and autoprefixer in postcss.config.js in standalone CLI (#8769)
Fix using special-characters as prefixes (#8772)
Don’t prefix classes used within arbitrary variants (#8773)
Add more explicit types for the default theme (#8780)

`v3.1.4`

Fixed

Provide default to <alpha-value> when using theme() (#8652)
Detect arbitrary variants with quotes (#8687)
Don’t add spaces around raw / that are preceded by numbers (#8688)

`v3.1.3`

Fixed

Fix extraction of multi-word utilities with arbitrary values and quotes (#8604)
Fix casing of import of corePluginList type definition (#8587)
Ignore PostCSS nodes returned by addVariant (#8608)
Fix missing spaces around arithmetic operators (#8615)
Detect alpha value in CSS theme() function when using quotes (#8625)
Fix "Maximum call stack size exceeded" bug (#8636)
Allow functions returning parallel variants to mutate the container (#8622)
Remove text opacity CSS variables from ::marker (#8622)

`v3.1.2`

Fixed

Ensure \ is a valid arbitrary variant token (#8576)
Enable postcss-import in the CLI by default in watch mode (#8574, #8580)

`v3.1.1`

Fixed

Fix candidate extractor regression (#8558)
Split ::backdrop into separate defaults group (#8567)
Fix postcss plugin type (#8564)
Fix class detection in markdown code fences and slim templates (#8569)

`v3.1.0`

We just released Tailwind CSS v3.1 — the first new feature release since v3.0 came out last year!

Read the announcement post for all the details, and watch the YouTube video for a tour of some of the highlights.

Added

Support PostCSS Document nodes (#7291)
Add text-start and text-end utilities (#6656)
Support customizing class name when using darkMode: 'class' (#5800)
Add --poll option to the CLI (#7725)
Add new border-spacing utilities (#7102)
Add enabled variant (#7905)
Add TypeScript types for the tailwind.config.js file (#7891)
Add backdrop variant (#7924, #8526)
Add grid-flow-dense utility (#8193)
Add mix-blend-plus-lighter utility (#8288)
Add arbitrary variants (#8299)
Add experimental matchVariant API (#8310, 34fd0fb8)
Add prefers-contrast media query variants (#8410)
Add opacity support when referencing colors with theme function (#8416)
Add postcss-import support to the CLI (#8437)
Add optional variant (#8486)
Add <alpha-value> placeholder support for custom colors (#8501)

Fixed

Types: allow for arbitrary theme values (for 3rd party plugins) (#7926)
Don’t split vars with numbers in them inside arbitrary values (#8091)
Require matching prefix when detecting negatives (#8121)
Handle duplicate At Rules without children (#8122)
Allow arbitrary values with commas in @apply (#8125)
Fix intellisense for plugins with multiple @apply rules (#8213)
Improve type detection for arbitrary color values (#8201)
Support PostCSS config options in config file in CLI (#8226)
Remove default [hidden] style in preflight (#8248)
Only check selectors containing base apply candidates for circular dependencies (#8222)
Rewrite default class extractor (#8204)
Move important selector to the front when @apply-ing selector-modifying variants in custom utilities (#8313)
Error when registering an invalid custom variant (#8345)
Create tailwind.config.cjs file in ESM package when running init (#8363)
Fix matchVariants that use at-rules and placeholders (#8392)
Improve types of the tailwindcss/plugin (#8400)
Allow returning parallel variants from addVariant or matchVariant callback functions (#8455)
Try using local postcss installation first in the CLI (#8270)
Allow default ring color to be a function (#7587)
Don't inherit to value from parent gradients (#8489)
Remove process dependency from log functions (#8530)
Ensure we can use @import 'tailwindcss/...' without node_modules (#8537)

Changed

Only apply hover styles when supported (future) (#8394)
Respect default ring color opacity (future) (#8448, 3f4005e)

microsoft/TypeScript (typescript)

`v5.6.3`: TypeScript 5.6.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.6.2`: TypeScript 5.6

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.5.4`: TypeScript 5.5.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

npm
NuGet package (soon!)

`v5.5.3`: TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.5.2`: TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

npm

`v5.4.5`: TypeScript 5.4.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.4.4`: TypeScript 5.4.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.4.3`: TypeScript 5.4.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.4.2`: TypeScript 5.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.3.3`: TypeScript 5.3.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.3.2`: TypeScript 5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.2.2`: TypeScript 5.2

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.1.6`: TypeScript 5.1.6

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on npm

`v5.1.5`: TypeScript 5.1.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.1.3`: TypeScript 5.1.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.0.4`: TypeScript 5.0.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.0.3`: TypeScript 5.0.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.0.2`: TypeScript 5.0

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.9.5`: TypeScript 4.9.5

For release notes, check out the release announcement.

Downloads are available on:

Changes:

69e88ef Port ignore deprecations to 4.9 (#52419)
daf4e81 Port timestamp fix to 4.9 (#52426)

`v4.9.4`: TypeScript 4.9.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript v4.9.4.

Downloads are available on:

Changes:

e286821 Bump version to 4.9.4 and LKG.
eb5419f Cherry-pick #51704 to release 4.9 (#51712)
b4d382b Cherry-pick changes for narrowing to tagged literal types.
e7a02f4 Port of #51626 and #51689 to release-4.9 (#51627)
1727912 Cherry-pick fix around visitEachChild to release-4.9. (#51544)

This list of changes was auto generated.

`v4.9.3`: TypeScript 4.9

For release notes, check out the release announcement.

Downloads are available on:

Changes:

93bd577 Bump version to 4.9.3 and LKG.
107f832 Update LKG.
31bee56 Cherry-pick PR #50977 into release-4.9 (#51363) [ #50872 ]
1e2fa7a Update version to 4.9.2-rc and LKG.
7ab89e5 Merge remote-tracking branch 'origin/main' into release-4.9
e5cd686 Update package-lock.json
8d40dc1 Update package-lock.json
5cfb3a2 Only call return() for an abrupt completion in user code (#51297)
a7a9d15 Fix for broken baseline in yieldInForInInDownlevelGenerator (#51345)
7f8426f fix for-in enumeration containing yield in generator (#51295)

See More

3d2b401 Fix assertion functions accessed via wildcard imports (#51324)
64d0d5a fix(51301): Fixing an unused import at the end of a line removes the newline (#51320)
754eeb2 Update CodeQL workflow and configuration, fix found bugs (#51263)
d8aad26 Update package-lock.json
d4f26c8 fix(51245): Class with parameter decorator in arrow function causes "convert to default export" refactoring failure (#51256)
16faf45 Update package-lock.json
8b1ecdb fix(50654): "Move to a new file" breaks the declaration of referenced variable (#50681)
170a17f Dom update 2022-10-25 (#51300)
9c4e14d Remove "No type information for this code" from baseline (#51311)
88d25b4 fix(50068): Refactors trigger debug failure when JSX text has a ' and a tag on the same line. (#51299)
8bee69a Update package-lock.json
702de1e Fix early call to return/throw on generator (#51294)
2c12b14 Add a GH Action to file a new issue if we go a week without seeing a typescript-error-deltas issue (#51271)
6af270d Update package-lock.json
2cc4c16 Update package-lock.json
6093491 Fix apparent typo in getStringMappingType (#51248)
61c2609 Update package-lock.json
ef69116 Generate shortest rootDirs module specifier instead of first possible (#51244)
bbb42f4 Fix typo in canWatchDirectoryOrFile found by CodeQL (#51262)
a56b254 Include 'this' type parameter in isRelatedTo fast path (#51230)
3abd351 Fix super property transform in async arrow in method (#51240)
eed0511 Update package-lock.json
2625c1f Make the init config category order predictable (#51247)
1ca99b3 fix(50551): Destructuring assignment with var bypasses "variable is used before being assigned" check (2454) (#50560)
3f28fa1 Update package-lock.json
906ebe4 Revert structuredTypeRelatedTo change and fix isUnitLikeType (#51076)
8ac4652 change type (#51231)
245a02c fix(51222): Go-to-definition on return statements should jump to the containing function declaration (#51227)
2dff34e markAliasReferenced should include ExportValue as well (#51219)
5ef2634 Update package-lock.json
d0f0e35 Remove old tslint comments (#51220)
85d405a Fixed a false positive "await has no effect on the type" diagnostic with mixed generic union (#50833)
1f8959f fix: avoid downleveled dynamic import closing over specifier expression (#49663)
11066b2 Rename internal functions to narrowTypeBySwitchOnTypeOf and narrowTypeByInKeyword (#51215)
4c9afe8 Update package-lock.json
f25bcb7 fix(49196): add jsdoc snippet for interface member functions (#51135)
7406ee9 fix(51170): Completing an unimplemented property overwrites rest of line (#51175)
a1d82fc Remove some unnecessary code discovered by rollup (#51204)
0481773 LEGO: Merge pull request 51200
98c19cb LEGO: Merge pull request 51190
13c9b05 Update package-lock.json
673475e Update package-lock.json
f6cf510 Add more tracing to node16/nodenext resolution (#51168)
83c5581 Update package-lock.json
be5f0fe Add an extra regression test for awaited unresolvable recursive union (#51167)
2cb7e77 fix(50416): correctly names disabled export refactors (#50663) [ #50416 ]
2bcfed0 feat(37440): Provide a quick-fix for non-exported types (#51038)
a24201c Remove VSDevMode.ps1 and createPlaygroundBuild (#51166)
2da62a7 fix(51112): omit parameter names that precede the type (#51142)
cf1b6b7 feat(51163): show QF to fill in the missing properties for the mapped type. (#51165)
bdcc240 Remove bug-causing carve-out in conditional type instantiation that hopefully is no longer required (#51151)
37317a2 Check nested weak types in intersections on target side of relation (#51140)
9f49f9c Update package-lock.json
4f54e7e Fix isExhaustiveSwitchStatement to better handle circularities (#51095)
503604c Overloads shouldn't gain @deprecated tags of other overloads in quick info (#50904)
e14a229 Update package-lock.json
67256e5 Remove unused declarations array in extractSymbol's TargetRange (#51091)
9c87ded fix(51100): ensure tsserver shuts down when parent process is killed (#51107)
c01ae01 Fix nightly publish oops in Gulpfile (#51131)
a7d10f1 Update package-lock.json
d0bfd8c fix(51072): ts.preProcessFile finds import in template string after conditional expression with template strings (#51082)
ad56b5c Convert scripts/Gulpfile to checked mjs/cjs so they can run without compilation (#50988)
dbeae5d fix(51017): Make lineText in the references response opt-out (#51081)
d06a592 Properly defer resolution of mapped types with generic as clauses (#51050)
42b1049 Update package-lock.json
5f3e6cc Plugin probe location is higher priority than peer node_modules (#51079) [ #34616 ]
2648f6a Plugins in project were adding up after every config file reload (#51087)
c18791c Fix incorrect options type to WatchOptions (#51064)
b0795e9 Update package-lock.json
43c6fd4 Covert some of the config testing to baselines for easy validation (#51063)
fc5e72b Remove unused defaultWatchFileKind method since useFsEvents is default for tsserver and tsc (#51044)
8af9a93 Use typescript.d.ts in APISample tests (#51061)
4953316 Remove configureLanguageServiceBuild, instrumenter (#51048)
9dfffd0 Update GitHub Actions (#51045)
4635a5c Update package-lock.json
33a34e5 Adding a JSDoc comment to the es5 type declarations to describe the functionality of Date.now() (#50630)
299745c Fix crash in goto-def on @override (#51016)
7dcf11f fix(50750): Object type literal with string literal property in contextual typing position causes language service error on all literal type references (#50757)
5cd49f6 Update package-lock.json
8a1b858 Update package-lock.json
96894db Include type parameter defaults in contextual typing (#50994) [ #51002 ]
0d0a793 Allow Unicode extended escapes in ES5 and earlier (#50918)
58bae8d Update package-lock.json
0ce72ef Add option to OrganizeImports for removal only (#50931)
42f9143 feat: codefix for for await of (#50623)
ecf50e8 Properly compute SymbolFlags.Optional for intersected properties (#50958)
d1586de Fully resolve aliases when checking symbol flags (#50853)
45148dd Update LKG to 4.8.4 (#50987)
9a83f25 Update package-lock.json
865848f Fix <= and > comparisons when compared against prerelease versions (#50915)
fbfe934 Fix comparability between type parameters related by a union constraint (#50978)
b09e93d Merge pull request #50041 from microsoft/fix/47969
0ac12bb Update package-lock.json
8192d55 Pick correct compilerOptions when checking if we can share emitSignatures (#50910) [ #50902 ]
16faef1 During uptodate ness check with buildInfo, check if there are errors explicitly with noEmit (#50974) [ #50959 ]
63791f5 Update package-lock.json
09368bc Handle if project for open file will get recollected because of pending cleanup from closed script info (#50908) [ #50868 ]
c81bf4d fix(49594): Typescript 4.7.3 bracketed class property compilation error strictPropertyInitialization:true (#49619)
bc9cbbe Merge pull request #49912 from microsoft/fix/47508
5a10f46 Update package-lock.json
8e71f42 Fixing pr comments
c100c64 Update package-lock.json
2a91107 Update package-lock.json
4ab9e76 Use paths in package.json 'files' array that work with npm 6 and later. (#50930)
549b542 Use paths in package.json 'files' array that work with npm 6 and later.
7f37d25 Update version to 4.9.1-beta and LKG.
f16ca7d Remove 'async' dependency, used only in errorCheck.ts, modernize file (#50667)
c6bef3f LEGO: Merge pull request 50921
6753027 Update package-lock.json
9740bcc Pluralized hasInvalidatedResolution -> hasInvalidatedResolutions (#50912)
84c29cd 🤖 Pick PR #50912 (Pluralized `hasInvalidatedResolutio...) into release-4.9 (#50913)
a26f634 Merge remote-tracking branch 'origin/main' into release-4.9
a455955 Make hasInvalidatedResolution non internal for program and add it watchApi (#50776) [ #48057 ]
645d1cd Fix assert in addIndirectUser in FAR (#50905)
bbec17d LEGO: Merge pull request 50900
a9ecc67 Update package-lock.json
221cf55 package.json exports should have priority over typesVersions (#50890)
acb8977 Remove .github/tsc.json (#50664)
7a3de81 fix(49993): skip the quick fix for an expression with an enum type (#50625)
2644f28 fix(49200): skip duplicated method declarations (#50609)
98652a3 Bump version to 4.9.0-beta and LKG.
4d91204 fix(37030): Expand Selection in function and arrow function skips body block (#50711)
e2dd508 DOM update 2022/09/21 (#50884)
1d9ab83 fix(50866): emit modifiers from export declarations (#50874)
92a1b12 LEGO: Merge pull request 50877
e383db6 Fix debug.ts __debugKind check (#50871)
01054e0 Consistently add undefined/missing to optional tuple element types (#50831)
d90795e Improve escape sequence handling in private names (#50856)
938a69a Fix import statement completions followed by interface declaration (#50350)
e002159 feat(49962): Disallow comparison against NaN (#50626)
80ae43d Fixing spaces
abc58bd Fixing baseline errors
305f4bd Merge branch 'main' into fix/47969
23746af fix(50591): RangeError: Maximum call stack size exceeded (#50594)
168186f Allow a union property of a private/protected member and an intersection property including that same member (#50328)
812ebcf Update package-lock.json
16156b1 Add rules from eslint's recommended set that triggered good lints (#50422)
a11c416 Improve checking of in operator (#50666)
67f2b62 Gabritto/jsemitfixsilly (#50849)
3014dec Don't elide imports when transforming JS files (#50404)
57c7aa7 LEGO: Merge pull request 50842
48a8e89 Improve check of whether type query node possibly contains reference to type parameter (#50070)
af9ced1 LEGO: Merge pull request 50825
a8e13f7 Fixed an issue with destructured bindings from a generic union constraint not being narrowed correctly (#50221)
08af0b6 Update package-lock.json
0df46e8 Fix test around RegExp match vs. exec results (#50813)
906510e Fixes for pr
2970c5d make RegExpExecArray always include index 0 (#50713)
0507192 Accepting baselines
29e50b3 Rewording documentation
01cae69 fix(50796): omit questionToken in object literal method completions (#50802)
3b84f76 Fix crash caused by incorrect bounds check (regression in 4.8) (#50797)
7e51306 Update package-lock.json
8b35c13 The error "Object is possibly null or undefined" is ambiguous. (#49797)
a3f51b3 Update user baselines +cc @sandersn (#43554)
ba10a0d Removing duplicated code
ec6ae1c Partially revert #41044, restoring parameter destructurings in d.ts files (#50779)
28232ca LEGO: Merge pull request 50783
49cfa1d Update package-lock.json
4110b80 Fix equality narrowing and comparable relation for intersections with {} (#50735)
b23f1d6 LEGO: Merge pull request 50771
618fb2d Update package-lock.json
08b91f6 fix(50717): tsc crashes when it sees a JSDoc tag inside an @override annotation (#50724)
60963d7 Discriminant of type never should never be matched (#50755)
e37ea53 Update package-lock.json
a88c366 Fix test baselining for tsserver host timeouts (#50748)
6d38487 Fix workflow typo (#50746)
6b890f9 Handle more places where package direcroy is converted to canonical file path (#50740)
f5f2923 Revert removal of nonInferrableAnyType (#50691)
7120b52 Update twoslash workflow (#50738)
68d526c Don't run linter after tests runs (#50597)
8e5e2e0 Fix backticks in our JSDoc comments (#50737)
a4cabe7 Support for auto-accessor fields from the Stage 3 Decorators proposal (#49705)
7737473 Update package-lock.json
12ab0fe Update package-lock.json
eb40134 Don't leave space for property access on non-integer literals (#50703)
a70bb9d Preserve special intersections in mapped types (#50704)
1a1c271 Don't remove space before dot if in property access on numeric literal (#50695)
7c918fb Baseline host state when baselining tsserver tests (#50678)
2f1ba45 Update LKG and devDep of typescript to v4.8.3 (#50689)
be4e9ba Update package-lock.json
f46a680 Remove error message in node16 (#50673)
ab831d0 Ignore --help and -? in tsc init generated compilerOptions (#50628)
bb6f36f Forward intersection state flag to conditional type target check (#50620)
b58721f Update package-lock.json
3c3820b Simplify CI detection (#50661)
9ac1fce Fix eslint not looking at certain scripts, fix lints (#50660)
fd05c0c Make useFsEvents as default strategy for the watching (#50366)
5c2f770 Remove unused cancellation from build (#50658)
66fbf05 Update package-lock.json
7910c50 Update package-lock.json
fd3a84c Report every instance of TS1208 (#50101)
62f980a Check if its same buildinfo only for directly referenced projects and not recursively (#50617) [ #50545 ]
856c7c5 Allow {} to narrow in same special cases as unknown (#50601)
854d448 in operator shouldn't narrow {} originating in unknown (#50610)
549e61d Update package-lock.json
bcf9949 fix(50079): show deprecated on JSX attributes (#50084)
5df09a5 Use bidirectional comparability in narrowing (#50592)
891cdc5 Remove unused baselines (#50593)
6db2c88 {} & null and {} & undefined should always be never (#50553)
238c341 Defer distributing index over generic object types (#50540)
2983092 Do not canonicalize the file names when getting absolute paths during nodenext resolution (#50557) [ #50544 ]
dcade77 Update package-lock.json
a9797d2 fix(50340): typeof ... === "undefined" check on discriminated union of undefined and object type doesn't narrow correctly (#50344)
43f8ae6 Only normalize intersections that include {} (#50535)
d293e72 Rename API to importPlugin (#50554)
cd312d3 Managing control flow
19defbf Update package-lock.json
f071d30 Move contributing related info out of README to CONTRIBUTING (#50543)
488d0ee Retain name and propertyName in declaration emit copies of binding patterns if property name is a keyword (#50537)
8b482b5 Update package-lock.json
c89f355 Remove redundant pretest script (#50518)
6d170b4 Handle intersections in isGenericTypeWithoutNullableConstraint (#50497)
ed6889c LEGO: Merge pull request 50506
29cbfe9 LEGO: Merge pull request 50493
6faa291 LEGO: Merge pull request 50484
71b2ba6 Reuse computed type of condition expressions (#49881)
8778c1d Update package-lock.json
4579245 fix(50427): allow convert function expressions (#50430)
cbc0b17 Push package-lock.json updates via typescript-bot token (#50476)
bb3a7ae fix(50415): Language server debug failure - Did not expect GetAccessor to have an Identifier in its trivia (#50470)
3557092 Rephrase error message to be 100% technically correct (#50471)
71d1911 add unknown to DateTimeFormatTypes (#50402)
8f89599 Don't include .gitattributes in package (#50475)
6e8337e Optimize substitution types (#50397)
226dd0b Fix typechecking related lints that changed post 4.8, update LKG to 4.8.2 (#50472)
164dddc feat(7481): Operator to ensure an expression is contextually typed by, and satisfies, some type (#46827)
0715791 Update package-lock.json
e675ea8 Remove AUTHORS.md, .mailmap, authors.ts script (#50410)
38076df Fix auto import crash due to difference in paths handling (#50419)
12eb519 fix(50435): Duplicate seeming Code Actions for convert const to let (#50442)
a08b045 Jsdoc property description (#50269) [ #47933 ]
5ba22e0 Remove top level loc folder (#50421)
c4eb37c Update package-lock.json
8d7ad8c fix(50375): Errors for missing enum-named properties should attempt to preserve names (#50382)
fb717df Discard union types before considering weak type checks on unit-like types (#50423)
b9a5bbc Syntax operations also need to ensure project is present for the open script infos since update could be pending to make sure open script info has project (#50418) [ #50131 ]
1d4fbbb Update package-lock.json
44ce3cf fix(50224): Intellisense for strings within a type's Union doesn't work properly for JSX (#50231)
6ee5db9 Use package.json files array instead of .npmignore (#50408)

This list of changes was auto generated.

`v4.8.4`: TypeScript 4.8.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.8.3`: TypeScript 4.8.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.8.2`: TypeScript 4.8

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.7.4`: TypeScript 4.7.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.7.3`: TypeScript 4.7.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.7.2`: TypeScript 4.7.2

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.6.4`: TypeScript 4.6.4

This release includes a bug fix for text formatting on certain ranges, which was impacting Visual Studio users.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.6.3`: TypeScript 4.6.3

This release includes fixes for

For the complete list of fixed issues, check out the

Downloads are available on:

npm

`v4.6.2`: TypeScript 4.6.2

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.5.5`: TypeScript 4.5.5