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

`v6.6.3`

Bug Fixes

add vitest import when extending vitest matchers (#646) (5ba0156)

`v6.6.2`

Bug Fixes

remove recursive type reference in vitest types (#636) (4468378)

`v6.6.1`

Bug Fixes

fix lodash import in to-have-selection.js (#642) (ced792e)

`v6.6.0`

Features

implement toHaveSelection (#637) (9b14804)

`v6.5.0`

Features

toHaveValue: Asserting aria-valuenow (#479) (acbf416)

`v6.4.8`

Bug Fixes

Drop peerDependencies from package.json (#610) (faf534b)

`v6.4.7`

Bug Fixes

Type definition of toHaveClass (#611) (5cc6298)

Bug Fixes

add js suffix to isEqualWith import (#599) (e8c8b13)

`v6.4.4`

Bug Fixes

infra: codecoverage token addition (#600) (f03a582)

`v6.4.3`

Bug Fixes

Updates role support for aria-required attribute in toBeRequired (#590) (20aca33)

`v6.4.2`

Bug Fixes

Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#575) (a93c0c4)

`v6.4.1`

Bug Fixes

Export type TestingLibraryMatchers from "./matchers" (#576) (dd1c4dd)

`v6.4.0`

Features

Add toHaveRole matcher (#572) (f7dc673)

`v6.3.0`

Features

Support for regular expressions in toHaveClass (#563) (9787ed5)

`v6.2.1`

Bug Fixes

Standalone types for "./matchers" export and add Bun support (#566) (5675b86)

`v6.2.0`

Features

toHaveAccessibleDescription supports aria-description (#565) (1fb156c)

`v6.1.6`

Bug Fixes

Upgrade @adobe/css-tools to v4.3.2 (#553) (b64b953)

`v6.1.5`

Bug Fixes

support uppercase custom props in toHaveStyle (#552) (b7b7c6a)

`v6.1.4`

Bug Fixes

upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#532) (44f1eab)

`v6.1.3`

Bug Fixes

proper @jest/globals import (#530) (5b492ac)

`v6.1.2`

Bug Fixes

bump @adobe/css-tools for ESM support (#525) (b959a68)

`v6.1.1`

Bug Fixes

package.json: update main and module file paths (#523) (853a3e5)

`v6.1.0`

Features

Publish ESM and CJS (https://github.com/testing-library/jest-dom/pull/519)

`v6.0.1`

Bug Fixes

matchers type is making the global expect unsafe (#513) (bdb34f1)

`v6.0.0`

Features

local types, supporting jest, @jest/globals, vitest (#511) (4b764b9)

BREAKING CHANGES

Removes the extend-expect script. Users should use
the default import path or one of the new test platform-specific
paths to automatically extend the appropriate "expect" instance.

extend-expect was not documented in the Readme, so this change should
have minimal impact.

Users can now use the following import paths to automatically extend
"expect" for their chosen test platform:

@testing-library/jest-dom - jest (@types/jest)
@testing-library/jest-dom/jest-globals - @jest/globals
@testing-library/jest-dom/vitest - vitest

For example:

import '@testing-library/jest-dom/jest-globals'

Importing from one of the above paths will augment the appropriate
matcher interface for the given test platform, assuming the import
is done in a .ts file that is included in the user's tsconfig.json.

It's also (still) possible to import the matchers directly without
side effects:

import * as matchers from '@testing-library/jest-dom/matchers'

Update kcd-scripts
Drop node < 14

testing-library/react-testing-library (@testing-library/react)

`v16.3.0`

Features

add bernardobelchior as a contributor for code, and doc (#1391) (9fc6a75)

`v16.2.0`

Features

Add support for React error handlers (#1354) (9618c51)

`v16.1.0`

Features

Add support for React 19 (#1367) (85ac253)

`v16.0.1`

Bug Fixes

Add support for exactOptionalPropertyTypes in TypeScript (#1351) (3dcd8a9)

`v16.0.0`

Features

Move @testing-library/dom and @types/react-dom to peer dependencies (#1305) (a4744fa)

BREAKING CHANGES

@testing-library/dom was moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of @testing-library/dom installed that frequently caused bugs when used with @testing-library/user-event. We will also be able to allow new versions of @testing-library/dom being used without a SemVer major release of @testing-library/react by just widening the peer dependency.
@types/react-dom needs to be installed if you're typechecking files using @testing-library/react.

`v15.0.7`

Bug Fixes

Ensure act is not any when React.act is not declared (#1323) (c1f2957)

`v15.0.6`

Bug Fixes

export new act when available (#1319) (b6e59f7)

`v15.0.5`

Bug Fixes

Stop restricting container option based on hydrate (#1313) (d143f46)

`v15.0.4`

Bug Fixes

Ensure renderHook options extend options for render (#1308) (48282c2)

`v15.0.3`

Bug Fixes

Don't raise TypeScript errors when hydating document (#1304) (067d0c6)

`v15.0.2`

Bug Fixes

Improve legacyRoot error message (#1301) (c63b873)

`v15.0.1`

Bug Fixes

Stop using nullish coalescing (#1299) (1645d21)

`v15.0.0`

Release

15.0.0 (#1295) (787cb85)

BREAKING CHANGES

Minimum supported Node.js version is 18.0
New version of @testing-library/dom changes various roles. Check out the changed tests in testing-library/dom-testing-library@2c57055 to get an overview about what changed.

tschaub/gh-pages (gh-pages)

`v6.3.0`

This relesae includes a fix for filenames starting with - and a number of dependency updates. See below for details.

#593 - Handle filenames starting with a dash (@sherlockdoyle)
#591 - Bump commander from 11.1.0 to 13.0.0 (@tschaub)
#587 - Bump eslint-config-tschaub from 14.1.2 to 15.1.0 (@tschaub)
#590 - Bump mocha from 10.8.2 to 11.0.1 (@tschaub)
#583 - Bump mocha from 10.7.3 to 10.8.2 (@tschaub)
#584 - Bump chai from 4.3.10 to 4.5.0 (@tschaub)

`v6.2.0`

Assorted dependency updates and a documentation change.

#581 - Update globby (@tschaub)
#578 - Bump sinon from 18.0.0 to 19.0.2 (@tschaub)
#579 - Bump eslint from 8.57.0 to 8.57.1 (@tschaub)
#576 - Bump async from 3.2.5 to 3.2.6 (@tschaub)
#573 - Bump mocha from 10.7.0 to 10.7.3 (@tschaub)
#571 - Bump mocha from 10.6.0 to 10.7.0 (@tschaub)
#569 - Bump mocha from 10.4.0 to 10.6.0 (@tschaub)
#563 - Bump braces from 3.0.2 to 3.0.3 (@tschaub)
#561 - Bump sinon from 17.0.2 to 18.0.0 (@tschaub)
#557 - Bump sinon from 17.0.1 to 17.0.2 (@tschaub)
#555 - Bump dir-compare from 4.2.0 to 5.0.0 (@tschaub)
#550 - Bump mocha from 10.3.0 to 10.4.0 (@tschaub)
#549 - Bump tmp from 0.2.1 to 0.2.3 (@tschaub)
#548 - Bump eslint from 8.56.0 to 8.57.0 (@tschaub)
#545 - Bump mocha from 10.2.0 to 10.3.0 (@tschaub)
#541 - fix: update instruction for next.js (@multivoltage)

`v6.1.1`

This release fixes an issue with the --cname option.

#535 - fix: Add missing cname option not passed to the config (@WillBAnders)
#539 - Bump eslint from 8.55.0 to 8.56.0 (@tschaub)

`v6.1.0`

This release adds support for --nojekyll and --cname options.

#531 - Bump sinon from 15.2.0 to 17.0.1 (@tschaub)
#529 - Bump async from 3.2.4 to 3.2.5 (@tschaub)
#524 - Bump commander from 11.0.0 to 11.1.0 (@tschaub)
#530 - Bump eslint from 8.49.0 to 8.53.0 (@tschaub)
#520 - Bump chai from 4.3.8 to 4.3.10 (@tschaub)
#527 - Bump actions/setup-node from 3 to 4 (@tschaub)
#533 - Add --nojekyll and --cname options (@tschaub)
#512 - Bump dir-compare from 4.0.0 to 4.2.0 (@tschaub)
#513 - Bump chai from 4.3.7 to 4.3.8 (@tschaub)
#515 - Bump actions/checkout from 3 to 4 (@tschaub)
#516 - Bump eslint from 8.46.0 to 8.49.0 (@tschaub)

`v6.0.0`

This release drops support for Node 14. Otherwise, there are no special upgrade considerations.

#507 - Dependency updates and drop Node 14 (@tschaub)
#495 - Bump sinon from 15.0.3 to 15.2.0 (@tschaub)
#500 - Bump semver from 6.3.0 to 6.3.1 (@tschaub)
#506 - Bump eslint from 8.38.0 to 8.46.0 (@tschaub)
#505 - Bump word-wrap from 1.2.3 to 1.2.5 (@tschaub)
#504 - Add error message when --dist is not specified. (@domsleee)
#473 - Bump fs-extra from 8.1.0 to 11.1.1 (@tschaub)
#477 - Bump eslint from 8.32.0 to 8.38.0 (@tschaub)
#474 - Bump sinon from 15.0.1 to 15.0.3 (@tschaub)
#440 - Update readme.md (@harveer07)

prettier/prettier (prettier)

`v3.6.2`

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

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

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

   1. Another
   2. List

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

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

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

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

   1. Another
   2. List

`v3.6.1`

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

// Input
export const version: string;

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

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

// Prettier 3.6.1
export const version: string;

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

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

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

`v3.6.0`

`v3.5.3`

`v3.5.2`

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

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

`v3.5.1`

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

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

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

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

`v3.5.0`

`v3.4.2`

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

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

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

C言
語
・
C++
・
Go
・
Rust

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

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

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

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

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

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

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

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

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

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

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

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

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

`v3.4.1`

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

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

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

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

`v3.4.0`

`v3.3.3`

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

This change adds clarity to operator precedence.

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

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

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

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

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

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

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

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

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

Adds support for Angular v18 @let declaration syntax.

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

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

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

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

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

`v3.3.2`

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

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

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

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

`v3.3.1`

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

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

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

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

Markdown

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

  - bar2

  - bar3
---

Markdown

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

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

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

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

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

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

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

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

`v3.3.0`

`v3.2.5`

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

Angular v17 supports single string inline styles.

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

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

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

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

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

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

// Prettier 3.2.4
const template = "foobar";

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

// Prettier 3.2.5
const template = "foobar";

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

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

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

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

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

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

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

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

`v3.2.4`

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

`v3.2.3`

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

// Input
1++;

// Prettier 3.2.2
1++;

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

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

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

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

Fix parser inference (#15927 by @fisker)

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

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

`v3.2.2`

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

For example this code would crash before:

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

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

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

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

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

`v3.2.1`

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

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

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

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

`v3.2.0`

`v3.1.1`