⬆️ Bump the testing group across 1 directory with 5 updates

[dependabot]

Bumps the testing group with 5 updates in the / directory:

Package	From	To
@testing-library/react	13.4.0	16.0.1
@testing-library/user-event	14.4.3	14.5.2
@vitejs/plugin-react	4.0.0	4.3.4
jsdom	21.1.0	25.0.1
vitest	0.31.1	2.1.8

Updates @testing-library/react from 13.4.0 to 16.0.1

Release notes

Sourced from @​testing-library/react's releases.

v16.0.1

16.0.1 (2024-08-29)

Bug Fixes

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

v16.0.0

16.0.0 (2024-06-03)

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

15.0.7 (2024-05-07)

Bug Fixes

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

v15.0.6

15.0.6 (2024-05-01)

Bug Fixes

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

v15.0.5

15.0.5 (2024-04-26)

Bug Fixes

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

v15.0.4

... (truncated)

Commits

• 3dcd8a9 fix: Add support for exactOptionalPropertyTypes in TypeScript (#1351)
• 7a28fa9 Fix React Canary and Experimental tests (#1353)
• a4744fa feat: Move @testing-library/dom and @types/react-dom to peer dependencie...
• c1f2957 fix: Ensure act is not any when React.act is not declared (#1323)
• b6e59f7 fix: export new act when available (#1319)
• f6a1677 chore: Adjust tests to workaround 18.3.0 bug (#1315)
• d143f46 fix: Stop restricting container option based on hydrate (#1313)
• 48282c2 fix: Ensure renderHook options extend options for render (#1308)
• 067d0c6 fix: Don't raise TypeScript errors when hydating document (#1304)
• c63b873 fix: Improve legacyRoot error message (#1301)
• Additional commits viewable in compare view

Updates @testing-library/user-event from 14.4.3 to 14.5.2

Release notes

Sourced from @​testing-library/user-event's releases.

v14.5.2

14.5.2 (2023-12-29)

Bug Fixes

• remove interop and deep DTL imports (6a3c896)

v14.5.1

14.5.1 (2023-09-15)

Bug Fixes

• incorrect default import from @​testing-library/dom (#1162) (d7483f0)

v14.5.0

14.5.0 (2023-09-14)

Bug Fixes

• exports: add a named export for userEvent (4019cee), closes #1146

Features

• types: Add additional type exports for UserEvent & Options (#1112) (da00e8d)

Commits

• d036279 chore: upgrade node in codesandbox
• 910fee5 chore: set tsconfig baseUrl
• fa8d867 revert: swap release script
• c4b4629 chore: upgrade testing environment
• 6a3c896 fix: remove interop and deep DTL imports
• d7483f0 fix: incorrect default import from @​testing-library/dom (#1162)
• 4be87b3 chore: swap release script
• d95121d chore: add --experimental-import-meta-resolve
• 8779eae chore: format, lint, fix lint
• 4019cee fix(exports): add a named export for userEvent
• Additional commits viewable in compare view

Updates @vitejs/plugin-react from 4.0.0 to 4.3.4

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.4

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

v4.3.3

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

v4.3.2

Ignore directive sourcemap error #369

v4.3.1

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.

v4.3.0

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.4 (2024-11-26)

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

4.3.3 (2024-10-19)

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

4.3.2 (2024-09-29)

Ignore directive sourcemap error #369

4.3.1 (2024-06-10)

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

... (truncated)

Commits

• 2e368a6 release: [email protected]
• bde1ad6 feat: add Vite 6 to peerDependencies range (#390)
• 45a727c fix(deps): update all non-major dependencies (#373)
• 5d2b6c6 fix: force non-legacy import attributes babel output (#386)
• b61592a release: [email protected]
• e8a923f fix: add react-dom in optimizeOps to handle CJS script. (#375)
• 7a7e339 feat: support new React Compiler target option (#374)
• 63b2e38 release: [email protected]
• fdf6ce4 fix(deps): update all non-major dependencies (#273)
• 4544e97 feat: update refresh utils for React Router 7 support (#363)
• Additional commits viewable in compare view

Updates jsdom from 21.1.0 to 25.0.1

Release notes

Sourced from jsdom's releases.

Version 25.0.1

• Updated dependencies, notably tough-cookie, which no longer prints a deprecation warning.

Version 25.0.0

This major release changes the prototype of a jsdom's EventTarget.prototype to point to the Object.prototype inside the jsdom, instead of pointing to the Node.js Object.prototype. Thus, the prototype chain of Window stays entirely within the jsdom, never crossing over into the Node.js realm.

This only occurs when runScripts is set to non-default values of "dangerously" or "outside-only", as with the default value, there is no separate Object.prototype inside the jsdom.

This will likely not impact many programs, but could cause some changes in instanceof behavior, and so out of an abundance of caution, we're releasing it as a new major version.

Version 24.1.3

• Fixed calls to postMessage() that were done as a bare property (i.e., postMessage() instead of window.postMessage()).

Version 24.1.2

• Fixed an issue with the in operator applied to EventTarget methods, e.g. 'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)
• Fixed the events fired by blur(): it no longer fires focus and focusin on the Document, and blur and focusout no longer have their relatedTarget property set. (asamuzaK)

Version 24.1.1

• Fixed selection methods to trigger the selectionchange event on the Document object. (piotr-oles)

Version 24.1.0

• Added the getSetCookie() method to the Headers class. (ushiboy)
• Fixed the creation and parsing of elements with names from Object.prototype, like "constructor" or "toString".
• Updated rweb-cssom, which can now parse additional CSS constructs.

Version 24.0.0

This release reverts our selector engine back to nwsapi. As discussed in #3659, the performance regressions from @asamuzakjp/dom-selector turned out to be higher than anticipated. In the future, we can revisit @asamuzakjp/dom-selector after it reaches nwsapi's performance on the two real-world benchmarks provided by the community.

Since reverting to nwsapi causes several functionality regressions, e.g. removing :has() support, we've decided to make this a major version.

Additionally:

• Small fixes to edge-case behavior of the following properties: input.maxLength, input.minLength, input.size, progress.max, tableCell.colSpan, tableCell.rowSpan, tableCol.span, textArea.cols, textArea.maxLength, textArea.minLength, textArea.rows.

Version 23.2.0

This release switches our CSS selector engine from nwsapi to @asamuzakjp/dom-selector. The new engine is more actively maintained, and supports many new selectors: see the package's documentation for the full list. It also works better with shadow trees.

There is a potential of a performance regression due to this change. In our stress test benchmark, which runs most of these 273 selectors against this 128 KiB document, the new engine completes the benchmark only 0.25x as fast. However, we're hopeful that in more moderate usage this will not be a significant issue. Any help speeding up @asamuzakjp/dom-selector is appreciated, and feel free to open an issue if this has had a significant impact on your project.

Version 23.1.0

• Added an initial implementation of ElementInternals, including the shadowRoot getter and the string-valued ARIA properties. (zjffun)
• Added the string-valued ARIA attribute-reflecting properties to Element.
• Fixed history.pushState() and history.replaceState() to follow the latest specification, notably with regards to how they handle empty string inputs and what new URLs are possible.
• Fixed the input.valueAsANumber setter to handle NaN correctly. (alexandertrefz)
• Updated various dependencies, including cssstyle which contains several bug fixes.

Version 23.0.1

• Fixed the incorrect canvas peer dependency introduced in v23.0.0.

Version 23.0.0

... (truncated)

Changelog

Sourced from jsdom's changelog.

25.0.1

• Updated dependencies, notably tough-cookie, which no longer prints a deprecation warning.

25.0.0

This major release changes the prototype of a jsdom's EventTarget.prototype to point to the Object.prototype inside the jsdom, instead of pointing to the Node.js Object.prototype. Thus, the prototype chain of Window stays entirely within the jsdom, never crossing over into the Node.js realm.

This only occurs when runScripts is set to non-default values of "dangerously" or "outside-only", as with the default value, there is no separate Object.prototype inside the jsdom.

This will likely not impact many programs, but could cause some changes in instanceof behavior, and so out of an abundance of caution, we're releasing it as a new major version.

24.1.3

• Fixed calls to postMessage() that were done as a bare property (i.e., postMessage() instead of window.postMessage()).

24.1.2

• Fixed an issue with the in operator applied to EventTarget methods, e.g. 'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)
• Fixed the events fired by blur(): it no longer fires focus and focusin on the Document, and blur and focusout no longer have their relatedTarget property set. (asamuzaK)

24.1.1

• Fixed selection methods to trigger the selectionchange event on the Document object. (piotr-oles)

24.1.0

• Added the getSetCookie() method to the Headers class. (ushiboy)
• Fixed the creation and parsing of elements with names from Object.prototype, like "constructor" or "toString".
• Updated rweb-cssom, which can now parse additional CSS constructs.

24.0.0

This release reverts our selector engine back to nwsapi. As discussed in #3659, the performance regressions from @asamuzakjp/dom-selector turned out to be higher than anticipated. In the future, we can revisit @asamuzakjp/dom-selector after it reaches nwsapi's performance on the two real-world benchmarks provided by the community.

Since reverting to nwsapi causes several functionality regressions, e.g. removing :has() support, we've decided to make this a major version.

Additionally:

• Small fixes to edge-case behavior of the following properties: input.maxLength, input.minLength, input.size, progress.max, tableCell.colSpan, tableCell.rowSpan, tableCol.span, textArea.cols, textArea.maxLength, textArea.minLength, textArea.rows.

23.2.0

This release switches our CSS selector engine from nwsapi to @asamuzakjp/dom-selector. The new engine is more actively maintained, and supports many new selectors: see the package's documentation for the full list. It also works better with shadow trees.

There is a potential of a performance regression due to this change. In our stress test benchmark, which runs most of these 273 selectors against this 128 KiB document, the new engine completes the benchmark only 0.25x as fast. However, we're hopeful that in more moderate usage this will not be a significant issue. Any help speeding up @asamuzakjp/dom-selector is appreciated, and feel free to open an issue if this has had a significant impact on your project.

23.1.0

• Added an initial implementation of ElementInternals, including the shadowRoot getter and the string-valued ARIA properties. (zjffun)

... (truncated)

Commits

• 04541b3 Version 25.0.1
• 96bd111 Update dependencies and dev dependencies
• d08440c Upgrade tough-cookie to v5.0.0
• c53efc8 Version 25.0.0
• 784c8a5 Set EventTarget.prototype to the jsdom's Object.prototype
• 0314f1e Version 24.1.3
• 46d5d5c Fix postMessage referenced as a bare property
• a241df6 Version 24.1.2
• c3a9aed Remove upstreamed WPTs
• 07fab37 Refactor Window object setup code
• Additional commits viewable in compare view

Updates vitest from 0.31.1 to 2.1.8

Release notes

Sourced from vitest's releases.

v2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @​sheremet-va (92f7a)

    View changes on GitHub

v2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @​sheremet-va (fbe5c)
  • This introduced some breaking changes (vitest-dev/vitest#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

v2.1.6

🚀 Features

• Support Vite 6

    View changes on GitHub

v2.1.5

   🐞 Bug Fixes

• dangerouslyIgnoreUnhandledErrors without base reporter  -  by @​AriPerkkio in vitest-dev/vitest#6808 (0bf0a)
• Capture unhandledRejection even when base reporter is not used  -  by @​AriPerkkio in vitest-dev/vitest#6812 (8878b)
• Don't change the working directory when loading workspace projects  -  by @​sheremet-va in vitest-dev/vitest#6811 (f0aea)
• Remove sequence.concurrent from the RuntimeConfig type  -  by @​sheremet-va in vitest-dev/vitest#6880 (6af73)
• Stop the runner before restarting, restart on workspace config change  -  by @​sheremet-va in vitest-dev/vitest#6859 (b01df)
• Don't rerun on Esc or Ctrl-C during watch filter  -  by @​hi-ogawa in vitest-dev/vitest#6895 (98f76)
• Print ssrTransform error  -  by @​hi-ogawa in vitest-dev/vitest#6885 (4c96c)
• Throw an error and a warning if .poll, .element, .rejects/.resolves, and locator.* weren't awaited  -  by @​sheremet-va in vitest-dev/vitest#6877 (93b67)
• browser:
  • Don't process the default css styles  -  by @​sheremet-va in vitest-dev/vitest#6861 (0d67f)
  • Support non US key input  -  by @​hi-ogawa in vitest-dev/vitest#6873 (5969d)
  • Stop the browser rpc when the pool is closed  -  by @​sheremet-va in vitest-dev/vitest#6858 (9a0c9)
  • Init browsers eagerly when tests are running  -  by @​sheremet-va in vitest-dev/vitest#6876 (417bd)
• coverage:
  • Report uncovered files when re-run by enter or 'a'  -  by @​AriPerkkio in vitest-dev/vitest#6848 (487c8)
• ui:
  • Remove crossorigin attributes for same origin assets  -  by @​hi-ogawa in vitest-dev/vitest#6883 (6e793)
• vite-node:
  • Improve esm check to decide external  -  by @​hi-ogawa in vitest-dev/vitest#6816 (7e1fa)
  • Top-level throw in module is not reported properly  -  by @​vanaigr and @​hi-ogawa in vitest-dev/vitest#6840 (cf0cb)
• vitest:
  • Use fetch() implementation from happy-dom  -  by @​capricorn86 in vitest-dev/vitest#6879 (3c56f)

   🏎 Performance

... (truncated)

Commits

• d69cc75 bump: 2.1.8
• 92f7a2a fix: support Node 21
• 81ed45b chore: release v2.1.7
• fbe5c39 fix: revert support for Vite 6
• b936702 bump: 2.1.6
• 32f23b9 chore: release v2.1.5
• 417bdb4 fix(browser): init browsers eagerly when tests are running (#6876)
• 93b67c2 fix: throw an error and a warning if .poll, .element, .rejects/`.resolv...
• 9a0c93d fix(browser): stop the browser rpc when the pool is closed (#6858)
• 251893b chore: set resolve.mainFields and resolve.conditions for SSR environment ...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #43.