chore(deps): update test packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/coverage-v8 (source)	2.0.5 -> 2.1.1
happy-dom	15.5.0 -> 15.7.4
vitest (source)	2.0.5 -> 2.1.1

---

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v2.1.1

   🐞 Bug Fixes

• browser:
  • Make example test callbacks async  -  by @​aqandrew in https://github.com/vitest-dev/vitest/issues/6484 (16aa7)
  • Optimize vitest-browser-vue correctly  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6490 (5cbb0)
• workspace:
  • Resolve glob pattern once to avoid name collision  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6489 (36b5a)

    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features

• api:
  • Make spec into a class instead of a tuple  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6355 (874a1)
• browser:
  • Move page.config to server.config, add more docs  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6252 (af2b8)
  • Make iframe scalable, improve documentation  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6257 (74ca1)
  • Introduce built-in locators  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6084 (3347f)
  • Support v8 coverage  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6273 (34199)
  • Support userEvent.upload in playwright provider  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6442 (cf148)
  • Support --inspect  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6433 (0499a)
  • Support --inspect-brk  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6434 (7ab0f)
• cli:
  • Extend existing list command to output only a list of file names  -  by @​Ma-hawaj and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6392 (008f0)
• coverage:
  • Add --exclude-after-remap  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6309 (5932a)
• mocker:
  • Introduce @​vitest/mocker package, allow { spy: true } instead of a factory  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6289 (95f02)
• vitest:
  • Add "provide" option  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6253 (4409d)
  • Add return type and promisable mockFactory  -  by @​syi0808 and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6139 (f5e0b)
  • Add vi.advanceTimersToNextFrame  -  by @​bnjm and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6347 (8ff63)
  • Allow env to be stubbed to undefined  -  by @​JSanchezIO and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6359 (c3b27)

   🐞 Bug Fixes

• Correctly resolve nested mocks with index file  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6266 (081cf)
• Don't panic when coverage.reporter is a string  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6267 (7b37d)
• Align RawMatcherFn type definition with Jest  -  by @​wheresrhys in https://github.com/vitest-dev/vitest/issues/6351 (d09f0)
• Cjs build of vite node server  -  by @​AkaraChen in https://github.com/vitest-dev/vitest/issues/6389 (12e70)
• Allow inlining vite's cached dependencies  -  by @​chriswheeldon-peakon in https://github.com/vitest-dev/vitest/issues/6284 (03208)
• Print unexpected error message if peer dependencies have a different version  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6446 (b992b)
• Ignore importer when resolving Vitest  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6469 (0b447)
• expect.getState().testPath always returns correct path  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6472 (ac698)
• UserEvent works consistently between providers  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6480 (0b4da)
• browser:
  • Print correct stack trace for unhandled errors  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6134 (1da6c)
  • Use documentElement as the root for selector  -  by @​sheremet-va (d8077)
  • Keep querying elements even if locator is created with elementLocator, add pubic @​vitest/browser/utils  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6296 (30dc5)
  • Produce valid config file if preview provider is used  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6305 (7f0ae)
  • Correctly run in-source tests in the browser  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6440 (c8531)
  • Exclude missed packages from optimization, print help message  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6445 (8d883)
  • Define mocker as a dependency  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6476 (9560a)
• coverage:
  • Warn if vitest and @vitest/* versions don't match  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6317 (e662c)
  • V8 to support source maps with multiple sources  -  by @​AriPerkkio and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6120 (1f6cb)
  • V8 to warn instead of crash when conversion fails  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6318 (91dea)
  • Use project specific vitenode for uncovered files  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6044 (da52d)
• runner:
  • Use performance.now instead of Date.now for duration  -  by @​LuciNyan in https://github.com/vitest-dev/vitest/issues/6382 (fe489)
  • Async assertion auto await should timeout  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6391 (ad6e7)
• snapshot:
  • Reject multiple toMatchInlineSnapshot updates at the same location  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6332 (1606f)
  • Improve inline snapshot inside loop rejection  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6339 (e0368)
• typecheck:
  • Run both runtime and typecheck tests if typecheck.include overlaps with include  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6256 (153ff)
• types:
  • Allow Callbacks Passed to before*/after* to Return Anything  -  by @​LuciNyan in https://github.com/vitest-dev/vitest/issues/6393 (f6217)
• ui:
  • Remove "filters" flickering  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6463 (0223b)
  • Render project name consistently  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6329 (94a18)
• vite-node:
  • Disable watcher if hmr is disabled  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6251 (c51c6)
  • Fix watch on vite 6  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6422 (c3ac4)
• vitest:
  • Update json reporter output  -  by @​Emiyaaaaa in https://github.com/vitest-dev/vitest/issues/6064 (c9979)
  • Add more type guards for --merge-reports  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6307 (0a5d8)
  • Always resolve vitest to the root version  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6369 (163d7)
  • Dispose vmForks listeners to avoid memory leak  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6448 (2673c)
• workspace:
  • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6316 (afdcb)

    View changes on GitHub

capricorn86/happy-dom (happy-dom)

v15.7.4

Compare Source

v15.7.3

Compare Source

👷‍♂️ Patch fixes

• Fixes bug that occurs when checking if a symbol property exists on HTMLSelectElement - By @​Cherry in task #​1526

v15.7.2

Compare Source

👷‍♂️ Patch fixes

• Fixes problem where it is not possible to observe again after disconnecting in MutationObserver - By @​capricorn86 in task #​1524

v15.7.1

Compare Source

👷‍♂️ Patch fixes

• Fixes selector validation and converts selectors to string (e.g. querySelector(['.class'])) - By @​capricorn86 in task #​1507

v15.7.0

Compare Source

v15.6.1

Compare Source

v15.6.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am on Monday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The update involves modifying the version of the happy-dom package in the package.json file multiple times, culminating in the final version being updated from 15.5.0 to 15.7.3. These changes reflect a series of upgrades to the library, which may include various enhancements, bug fixes, or performance improvements introduced in the newer versions.

Changes

File	Change Summary
package.json	Updated happy-dom version from 15.4.2 to 15.5.0, then from 15.5.0 to 15.6.0, from 15.6.0 to 15.6.1, from 15.6.1 to 15.7.0, from 15.7.0 to 15.7.2, and finally from 15.7.2 to 15.7.3

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant HappyDom

    User->>App: Request to use HappyDom
    App->>HappyDom: Initialize with version 15.7.3
    HappyDom-->>App: Return initialized instance
    App-->>User: Response with HappyDom functionality

Loading

Poem

🐇
In the garden where I hop and play,
A new version of joy has come our way!
Happy-dom, oh what a delight,
With upgrades that shine so bright.
Let’s dance and twirl, oh what fun,
For every change, a new day begun!
🌼

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/coverage-v8@2.1.1	Transitive: environment, filesystem, shell	+63	10.6 MB	antfu, oreanno, patak, ...1 more
npm/happy-dom@15.7.4	network, shell, unsafe	+3	9.8 MB	davidortner
npm/vitest@2.1.1	Transitive: environment, filesystem, shell, unsafe	+32	4.04 MB	antfu, oreanno, patak, ...1 more

🚮 Removed packages: npm/@vitest/coverage-v8@2.0.5, npm/happy-dom@15.5.0, npm/vitest@2.0.5

View full report↗︎

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cf86752 and e52743c.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• package.json

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e52743c and 9374534.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• package.json

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9374534 and e45f6d5.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• package.json

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e45f6d5 and cb13dd7.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• package.json

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cb13dd7 and 66d5c15.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• package.json