chore(deps): bump the unit-testing-config-deps group across 1 directory with 5 updates

[dependabot]

Bumps the unit-testing-config-deps group with 5 updates in the / directory:

Package	From	To
vitest	1.6.0	2.0.5
@testing-library/jest-dom	6.4.5	6.5.0
@testing-library/react	15.0.7	16.0.1
jsdom	24.0.0	25.0.0
vite-tsconfig-paths	4.3.2	5.0.1

Updates vitest from 1.6.0 to 2.0.5

Release notes

Sourced from vitest's releases.

v2.0.5

   🚀 Features

• Introduce experimental reported tasks  -  by @​sheremet-va in vitest-dev/vitest#6149 (13d85)
  • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

   🐞 Bug Fixes

• Show a difference between string characters if both values are strings  -  by @​sheremet-va in vitest-dev/vitest#6191 (29176)
• testNamePattern adds leading space  -  by @​AriPerkkio in vitest-dev/vitest#6186 (073a5)
• browser:
  • Don't bundle afterEach cleanup hooks in node entrypoint  -  by @​sheremet-va in vitest-dev/vitest#6192 (e6fbc)
  • UserEvent.setup initiates a separate state for userEvent instance  -  by @​sheremet-va in vitest-dev/vitest#6088 (883f3)
  • Correctly import optimized module in vi.importActual  -  by @​sheremet-va in vitest-dev/vitest#6219 (804ff)
  • Passing options to hover/unhover  -  by @​MNeverOff in vitest-dev/vitest#6175 (d4c00)
  • Improve unique CSS selector generation  -  by @​zacharyvoase and Zack Voase in vitest-dev/vitest#6243 (e7acd)
• vitest:
  • Remove nuxt from auto inline deps  -  by @​sheremet-va (93882)
  • Improve defineProject and defineWorkspace types  -  by @​sheremet-va in vitest-dev/vitest#6198 (8cd82)
  • Correctly resolve mocked node:* imports in __mocks__ folder  -  by @​sheremet-va in vitest-dev/vitest#6204 (a48be)
• web-worker:
  • Expose globals on self  -  by @​sheremet-va in vitest-dev/vitest#6170 (12bb5)

    View changes on GitHub

v2.0.4

   🐞 Bug Fixes

• One-line environment options  -  by @​hahanein in vitest-dev/vitest#5105 (38269)
• Resolve assets imported with require  -  by @​sheremet-va in vitest-dev/vitest#6159 (807a2)
• browser:
  • Don't panic if @​vitest/browser is installed outside of project root  -  by @​sheremet-va in vitest-dev/vitest#6135 (ccfcd)
  • Set global filepath  -  by @​sheremet-va in vitest-dev/vitest#6190 (0d0b4)
  • Allow preview and open in the editor screenshot error from ui  -  by @​userquin in vitest-dev/vitest#6113 (2d620)
• coverage:
  • Global thresholds to include files from glob thresholds  -  by @​thor-juhasz and @​AriPerkkio in vitest-dev/vitest#6172 (02e3f)
  • Consistent type-only file handling  -  by @​AriPerkkio in vitest-dev/vitest#6183 (90576)
  • Ignore *.cts files  -  by @​AriPerkkio in vitest-dev/vitest#6189 (5da45)
  • Add thresholds.<glob>.100 option  -  by @​thor-juhasz and @​AriPerkkio in vitest-dev/vitest#6174 (f6845)
• spy:
  • Fix mockImplementation for function overload and unions  -  by @​hi-ogawa in vitest-dev/vitest#6181 (7a75b)

    View changes on GitHub

v2.0.3

   🚀 Features

• ui: Show all suites/tests when parent matches  -  by @​userquin in vitest-dev/vitest#6106 (840e0)

   🐞 Bug Fixes

... (truncated)

Commits

• 99452a7 chore: release v2.0.5
• 9b9bdf7 chore: remove unnecessary await (#6249)
• 40dfad8 docs: add reported tasks docs (#6245)
• 13d85bd feat: introduce experimental reported tasks (#6149)
• b76a927 refactor(vitest): move public exports to public folder (#6218)
• 56dbfa6 refactor: make a distinction between node and runtime types (#6214)
• a48be6f fix(vitest): correctly resolve mocked node:* imports in mocks folder (#6204)
• 3aab8a1 refactor: deprecate all config types from the main Vitest entrypoint, introdu...
• 57d23ce docs: fix inconsistencies, remove low informative twoslash examples (#6200)
• 8cd8272 fix(vitest): improve defineProject and defineWorkspace types (#6198)
• Additional commits viewable in compare view

Updates @testing-library/jest-dom from 6.4.5 to 6.5.0

Release notes

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

v6.5.0

6.5.0 (2024-08-23)

Features

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

v6.4.8

6.4.8 (2024-07-23)

Bug Fixes

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

v6.4.7

6.4.7 (2024-07-22)

Bug Fixes

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

v6.4.6

6.4.6 (2024-06-10)

Bug Fixes

• Support @​starting-style (#602) (fd9ee68)

Commits

• 62f0e3a docs: add waynevanson as a contributor for code, and test (#626)
• acbf416 feat(toHaveValue): Asserting aria-valuenow (#479)
• 47a667c docs: add vorant94 as a contributor for code (#619)
• 06d19ba adjust vitest ambient declaration file according to vitest docs (#612)
• a073b08 docs: add aleks-elkin as a contributor for maintenance (#618)
• aa094a5 chore: remove unused @​babel/runtime dependency (#617)
• d02e80b docs: add ddolcimascolo as a contributor for maintenance (#616)
• faf534b fix: Drop peerDependencies from package.json (#610)
• 78a2934 docs: add tonyhallett as a contributor for bug (#615)
• 5cc6298 fix: Type definition of toHaveClass (#611)
• Additional commits viewable in compare view

Updates @testing-library/react from 15.0.7 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.

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...
• See full diff in compare view

Updates jsdom from 24.0.0 to 25.0.0

Release notes

Sourced from jsdom's releases.

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.

Changelog

Sourced from jsdom's changelog.

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.

Commits

• 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
• 3383805 Fix events fired by blur()
• 065abcb Roll web platform tests
• 439a43e Setup Window prototype in vm context
• Additional commits viewable in compare view

Updates vite-tsconfig-paths from 4.3.2 to 5.0.1

Release notes

Sourced from vite-tsconfig-paths's releases.

v5.0.0

This package is now ESM only in order to align with Vite: https://vitejs.dev/guide/migration#deprecate-cjs-node-api

If your project is using CommonJS, you can rename your Vite config to use the .mjs or .mts extension (depending on whether you use TypeScript or not). If you're not using Vite v5.0.0+, you may want to pin your dependency to v4 of this plugin.

Commits

• c2b0b4c 5.0.1
• ae80736 chore(fix): restore "main" and "types" fields in package.json
• 29093ed 5.0.0
• 66d478e chore: update readme notice
• 5ff0d6a chore: drop CJS build (#151)
• 03ffe4a chore: update readme announcement
• fc2da50 chore: update lockfiles
• See full diff in compare view

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 #144.