Search code, repositories, users, issues, pull requests...

Fixed fit-content prefix for Firefox.

`v10.4.19`

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

`v10.4.18`

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

`v10.4.17`

Fixed user-select: contain prefixes.

pnpm/action-setup (pnpm/action-setup)

`v2.4.1`

postcss/postcss (postcss)

`v8.4.49`

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

`v8.4.48`

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

`v8.4.47`

Removed debug code.

`v8.4.46`

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

`v8.4.45`

Removed unnecessary fix which could lead to infinite loop.

`v8.4.44`

Another way to fix markClean is not a function error.

`v8.4.43`

Fixed markClean is not a function error.

`v8.4.42`

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

`v8.4.41`

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

`v8.4.40`

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

`v8.4.39`

Fixed CssSyntaxError types (by @romainmenke).

`v8.4.38`

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

`v8.4.37`

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

`v8.4.36`

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

`v8.4.35`

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

`v8.4.34`

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

`v8.4.33`

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

`v8.4.32`

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

prettier/prettier (prettier)

`v3.4.2`

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

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

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

C言
語
・
C++
・
Go
・
Rust

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

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

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

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

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

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

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

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

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

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

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

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

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

`v3.4.1`

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

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

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

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

`v3.4.0`

`v3.3.3`

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

This change adds clarity to operator precedence.

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

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

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

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

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

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

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

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

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

Adds support for Angular v18 @let declaration syntax.

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

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

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

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

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

`v3.3.2`

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

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

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

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

`v3.3.1`

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

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

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

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

Markdown

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

  - bar2

  - bar3
---

Markdown

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

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

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

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

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

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

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

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

`v3.3.0`

`v3.2.5`

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

Angular v17 supports single string inline styles.

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

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

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

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

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

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

// Prettier 3.2.4
const template = "foobar";

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

// Prettier 3.2.5
const template = "foobar";

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

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

In v2.3.0, we introduced "jsonc" parser which adds trialing 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 .pretterrc file

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

`v3.2.4`

Fix incorrect parser inference (#15947 by @fisker)

Files like .eslintrc.json were incorrectly formatted as JSONC files.

// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }

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

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

sveltejs/prettier-plugin-svelte (prettier-plugin-svelte)

(fix) force quote style inside style directives
(fix) preserve commas in array expressions
(fix) Svelte 5: properly determine end of snippet parameters with TS annotations

`v3.2.6`

(feat) Svelte 5: never quote single-expression-attributes

`v3.2.5`

(fix) Svelte 5: format TypeScript in the template

`v3.2.4`

(fix) speed up regex

`v3.2.3`

(fix) don't force-self-close <slot> tags

`v3.2.2`

(fix) handle updated @render tag AST shape

`v3.2.1`

(fix) handle updated @render tag AST shape

`v3.2.0`

(feat) format JSON script tags
(feat) introduce separate entry point using prettier/standalone
(fix) don't duplicate comments of nested script/style tags
(fix) handle updated Snippet block AST shape

`v3.1.2`

(fix) handle > tags in attributes

`v3.1.1`

(fix) handle types on each/await contexts

`v3.1.0`

(feat) add experimental support for Svelte 5
(feat) support #snippet and @render

sveltejs/language-tools (svelte-check)

`v3.8.6`

fix: support Svelte 5 module script attribute (#2473)

`v3.8.5`

chore: bump html/css language service (#2424)
chore: better "cannot use bind:" error message (#2429)
fix: no implicit children prop when using slot (#2427)
fix: correctly handle HTML between implicit snippet props (#2450)
fix: correctly scope snippet declarations (#2449)
fix: make it possible to type snippet parameters using JSDoc (#2449)
fix: add legacy methods to own component shape (#2451)

`v3.8.4`

fix: ensure bindings and exports work properly for Svelte 5 + TS5.5

`v3.8.3`

fix: detect root snippets correctly
fix: prevent false positive store declarations (#2422)

`v3.8.2`

chore: reduce dependencies (#2413) (#2400)
fix: handle snippets with typed arguments (#2412)
fix: handle optional arguments in snippets (#2414)

`v3.8.1`

fix: adjust ambient module snipping logic
chore: speed up regex

`v3.8.0`

fix: allow for whitespace in snippets declaration (#2366)
fix: allow as expressions for bindable props (#2372)
fix: force correct semantic tokens for $props types (#2379)
feat: Svelte 5 component class/function interop (#2380)

`v3.7.1`

fix: rework bindable types strategy (#2361)

`v3.7.0`

feat: mark only properties as bindable that were declared using $bindable() in Svelte 5 runes mode (#2336)
chore: better Svelte 5 interop (#2336)
fix: preserve event attribute casing in Svelte 5 (#2347)
fix: handle #await inside #snippet (#2348)
fix: better bind:group transformation (#2349)
fix: handle boolean css var (#2350)

`v3.6.9`

fix: ensure type widening for bind:group
perf: improve perf in deleteUnresolvedResolutionsFromCache (#2320)
fix: adjust for moved compiler file in Svelte 5 (#2327)

`v3.6.8`

chore: support TypeScript 5.4 (#2313)
fix: allow falsy values for render tags

`v3.6.7`

fix: use type instead of generic for $props() (#2314)

`v3.6.6`

fix: adjust render tag for latest AST version

`v3.6.5`

fix: adjust $props() comment type logic (#2294)
fix: use Svelte 4 compiler from user when available
fix: adjust snippet helper type to new snippet API
fix: also take type argument into account when analyzing $props()
fix: don't add form type to zero types when property is not typed out

`v3.6.4`

fix: take type annotations into account when transforming one-way bindings (#2283)

Svelte 5:

fix: deduplicate generate props/events/slot types correctly (#2269)
fix: adjust snippet code generation for new AST shape (#2282)
fix: ensure correct types for media bindings (#2284)
fix: implict children tweaks (#2285) (#2263)

`v3.6.3`

fix: various snippet improvements
fix: don't remove non-null-assertion operator (#2248)
fix: prevent crash in moduleResolution Node16+ (#2230)
fix: correct declareMap reference line number (#2250)
feat: zero effort typings for reroute (#2252)

`v3.6.2`

feat: add best-effort fallback typings to $props() rune
fix: don't add generic type when snippet has no params
fix: pass children to zero types Svelte 5 (#2212)
fix: add possibility to pass in version to svelte2tsx to differentiate transpiler targets
fix: add implicit children prop in Svelte 5 mode (#2211)
fix: hide deprecation warnings in generated code Svelte 5 (svelte#9586)
chore: bump deps (#2214)
perf: faster checks for certain characters (#2179)

`v3.6.1`

fix: support SvelteKit zero types with $props rune
fix: use Snippet type and ensure @render tag only uses snippet functions
fix: account for > in attribute strings (#2204)
fix: handle contexts in each/await
fix: don't lowercase custom element attributes (#2190)
fix: make root snippets available in instance script (#2201)

`v3.6.0`

feat: add experimental compatibility for Svelte 5
fix: enhance numberOnlyAttributes list

tailwindlabs/tailwindcss (tailwindcss)

`v3.4.17`

`v3.4.16`

Fixed

Ensure the TypeScript types for PluginsConfig allow undefined values (#14668)

Changed

Bumped lilconfig to v3.x (#15289)

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

`v3.4.11`

`v3.4.10`

`v3.4.9`

Fixed

No longer warns when broad glob patterns are detecting vendor folders

`v3.4.8`

`v3.4.7`

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

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

`v3.4.2`