build(deps-dev): bump the vitest group across 1 directory with 2 updates - #9157
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
requested review from
acywatson,
etrepum,
fantactuka,
ivailop7,
potatowagon and
zurfyx
as code owners
September 11, 2026 16:40
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
meta-cla
Bot
added
the
CLA Signed
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-f0fe82b5e0
branch
from
September 11, 2026 21:53
f2cd225 to
b875b1d
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-f0fe82b5e0
branch
from
September 15, 2026 15:32
b875b1d to
666b9c2
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-f0fe82b5e0
branch
from
September 16, 2026 06:03
666b9c2 to
5a11f5e
Compare
Bumps the vitest group with 2 updates in the / directory: [@vitest/browser-playwright](https://github.com/vitest-dev/vitest/tree/HEAD/packages/browser-playwright) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/browser-playwright` from 4.1.11 to 5.0.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/browser-playwright) Updates `vitest` from 4.1.11 to 5.0.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/browser-playwright" dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: vitest - dependency-name: vitest dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: vitest ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-f0fe82b5e0
branch
from
September 16, 2026 22:28
5a11f5e to
1f424f8
Compare
etrepum
added a commit
to etrepum/lexical
that referenced
this pull request
Sep 16, 2026
…pter ## Description The initial fix for facebook#9157 duplicated the toHaveNoViolations assertion signature. Import the matcher object type from jest-axe and use its keys to select the existing signatures from jest.Matchers<R> instead. A Vitest module augmentation is still necessary because @types/jest-axe only augments Jest. The adapter now reuses the upstream assertion signatures and return types without importing unrelated Jest matchers. ## Test plan ### Before The original PR, before the stacked fix, failed `pnpm run tsc` with status 2: ```text packages/lexical-react/src/__tests__/unit/LexicalContentEditableElement.test.tsx(244,21): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalContentEditableElement.test.tsx(295,21): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(607,33): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(647,35): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(765,33): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(805,35): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. ``` The initial adapter passed these checks but manually repeated the matcher signature. ### After `pnpm run ci-check` passed with status 0: ```text $ npm-run-all --parallel tsc tsc-scripts tsc-extension tsc-website flow prettier lint $ tsc $ tsc -p ./tsconfig.scripts.json $ pnpm --filter @lexical/devtools run compile $ prettier --list-different . $ node ./scripts/check-flow-types.mjs $ pnpm --filter @lexical/website run tsc $ eslint ./ Running Flow... $ tsc -p tsconfig.json $ tsc --noEmit Found 0 errors ``` An isolated TypeScript compiler API probe also passed: ```text Matcher declarations pass with skipLibCheck=false; direct/not return void, resolves/rejects return Promise<void>, unknown matchers remain errors. Matcher keys and signatures match jest-axe types exactly. ``` Validated on Linux with Node 24.19.0 and Vitest 5.0.0. Runtime tests and browser/platform matrices were not rerun for this type-only refinement; the prior revision passed all 27 tests across the three relevant suites.
## Description Vitest 5 no longer inherits the global Jest matcher declarations from @types/jest-axe, so the accessibility assertions fail TypeScript checking even though the tests pass at runtime. Augment Vitest's Matchers interface in a declaration scoped to the React test utilities. Preserve the return type for direct and resolves/rejects assertions. The declaration is excluded from published type builds with the other test files. This commit is stacked directly on #9157 at 5a11f5e. ## Test plan ### Before `pnpm run tsc` exited with status 2: ```text packages/lexical-react/src/__tests__/unit/LexicalContentEditableElement.test.tsx(244,21): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalContentEditableElement.test.tsx(295,21): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(607,33): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(647,35): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(765,33): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(805,35): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. ``` ### After `pnpm run ci-check` exited with status 0: ```text $ npm-run-all --parallel tsc tsc-scripts tsc-extension tsc-website flow prettier lint $ node ./scripts/check-flow-types.mjs $ prettier --list-different . $ tsc -p ./tsconfig.scripts.json $ pnpm --filter @lexical/devtools run compile $ eslint ./ $ tsc Running Flow... $ pnpm --filter @lexical/website run tsc $ tsc --noEmit $ tsc -p tsconfig.json Found 0 errors ``` `pnpm run test-unit --maxWorkers=2 LexicalContentEditableElement LexicalNestedComposer LexicalExtensionEditorComposer` exited with status 0: ```text Test Files 3 passed (3) Tests 27 passed (27) ``` An isolated TypeScript compiler API probe with `skipLibCheck: false` also passed: ```text Matcher declarations pass with skipLibCheck=false; direct/not return void, resolves/rejects return Promise<void>, unknown matchers remain errors. ``` Validated on Linux with Node 24.19.0 and Vitest 5.0.0. Browser and other platform suites were not rerun; this change only adds a test type declaration.
…pter ## Description The initial fix for #9157 duplicated the toHaveNoViolations assertion signature. Import the matcher object type from jest-axe and use its keys to select the existing signatures from jest.Matchers<R> instead. A Vitest module augmentation is still necessary because @types/jest-axe only augments Jest. The adapter now reuses the upstream assertion signatures and return types without importing unrelated Jest matchers. ## Test plan ### Before The original PR, before the stacked fix, failed `pnpm run tsc` with status 2: ```text packages/lexical-react/src/__tests__/unit/LexicalContentEditableElement.test.tsx(244,21): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalContentEditableElement.test.tsx(295,21): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(607,33): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(647,35): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(765,33): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. packages/lexical-react/src/__tests__/unit/LexicalNestedComposer.test.tsx(805,35): error TS2339: Property 'toHaveNoViolations' does not exist on type 'Assertion<void, AxeResults>'. ``` The initial adapter passed these checks but manually repeated the matcher signature. ### After `pnpm run ci-check` passed with status 0: ```text $ npm-run-all --parallel tsc tsc-scripts tsc-extension tsc-website flow prettier lint $ tsc $ tsc -p ./tsconfig.scripts.json $ pnpm --filter @lexical/devtools run compile $ prettier --list-different . $ node ./scripts/check-flow-types.mjs $ pnpm --filter @lexical/website run tsc $ eslint ./ Running Flow... $ tsc -p tsconfig.json $ tsc --noEmit Found 0 errors ``` An isolated TypeScript compiler API probe also passed: ```text Matcher declarations pass with skipLibCheck=false; direct/not return void, resolves/rejects return Promise<void>, unknown matchers remain errors. Matcher keys and signatures match jest-axe types exactly. ``` Validated on Linux with Node 24.19.0 and Vitest 5.0.0. Runtime tests and browser/platform matrices were not rerun for this type-only refinement; the prior revision passed all 27 tests across the three relevant suites.
etrepum
approved these changes
Sep 17, 2026
dependabot
Bot
deleted the
dependabot/npm_and_yarn/vitest-f0fe82b5e0
branch
September 17, 2026 01:26
Merged
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the vitest group with 2 updates in the / directory: @vitest/browser-playwright and vitest.
Updates
@vitest/browser-playwrightfrom 4.1.11 to 5.0.0Release notes
Sourced from @vitest/browser-playwright's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)897f51fchore: release v5.0.0-rc.4 (#11107)dc10f5ffix(browser): report the action error when a task times out (#11101)7db80dcchore: release v5.0.0-rc.3 (#11089)af83d1bchore: release v5.0.0-rc.2 (#10976)c496c2efix(browser): fail instead of hanging when the browser stops responding (#10956)032d318fix(browser): trigger playwright/chromium gc on lower disk availability (#10912)a7fa111chore: release v5.0.0-rc.1 (#10920)0553851chore: add Knip checks (#10847)b7be731chore: release v5.0.0-beta.7 (#10825)Updates
vitestfrom 4.1.11 to 5.0.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)d46a747fix: treat test.describe as a suite during static collection (#11128)584cf30fix: add a warning if inline project has duplicate plugins due to unexpected ...f08ce4bfix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)