Skip to content

build(deps-dev): bump the testing group across 1 directory with 5 updates - #551

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/testing-0fd3bf0f6f
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/testing-0fd3bf0f6f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

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

Package From To
@nuxt/test-utils 4.3.3 4.3.4
@vitest/coverage-v8 5.0.4 5.1.0
happy-dom 20.14.6 21.0.4
playwright-core 1.64.1 1.65.0
vitest 5.0.4 5.1.0

Updates @nuxt/test-utils from 4.3.3 to 4.3.4

Release notes

Sourced from @​nuxt/test-utils's releases.

v4.3.4

v4.3.4 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes

  • runtime: test failure when module cached (#1856)
  • runtime-utils: support registerEndpoint with FormData in jsdom (#1846)
  • e2e: restore test context before running setup hooks (#1855)
  • e2e: apply nuxtConfig overrides to dev server (#1851)
  • config: prefer h3 version from nitro path (#1844)
  • module: apply vitest setup only when loaded from vitest config (#1834)
  • config: respect default resolve conditions in vitest browser mode (#1843)
  • module: pass required token to open vitest ui in devtools (#1841)

💅 Refactors

  • module: use package-manager-detector workspace + deno handling (1d59009c7)

🏡 Chore

  • cleanup example deps, unify vitest, and update knip config (#1840)

❤️ Contributors

Commits
  • a2a0174 v4.3.4 (#1838)
  • 8a372c7 fix(runtime): test failure when module cached (#1856)
  • eaf8b40 fix(runtime-utils): support registerEndpoint with FormData in jsdom (#1846)
  • 28f2639 chore(deps): update nuxt framework to v5.0.0-2610141459-ba5fba8 (#1858)
  • 33c8cac chore(deps): update nuxt framework to v5.0.0-2610132251-aadc393 (#1857)
  • e345739 fix(e2e): restore test context before running setup hooks (#1855)
  • cc855b4 chore(deps): update nuxt framework to v5.0.0-2610121449-e69fd4e (#1854)
  • c5294da chore(deps): update nuxt framework to v5.0.0-2610121141-fa50237 (#1853)
  • 9410fe8 fix(e2e): apply nuxtConfig overrides to dev server (#1851)
  • 6f68679 chore(deps): update nuxt framework to v5.0.0-2610111052-7bcb758 (#1852)
  • Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 5.0.4 to 5.1.0

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.1.0

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates happy-dom from 20.14.6 to 21.0.4

Release notes

Sourced from happy-dom's releases.

v21.0.4

👷‍♂️ Patch fixes

  • Fixed a code injection vulnerability in the ESM compiler - By @​capricorn86
  • Fixed cross-origin isolation so opaque-origin data: iframes cannot access their parent or top window - By @​capricorn86

v21.0.3

👷‍♂️ Patch fixes

  • Fixes security vulnerability where authorization header was forwarded when redirecting - By @​capricorn86

v21.0.2

👷‍♂️ Patch fixes

v21.0.1

👷‍♂️ Patch fixes

v21.0.0

💣 Breaking Changes

  • Disables CSS and IFrame loading by default to prevent server-side request forgery (SSRF) - By @​capricorn86
    • An attacker could embed <iframe> or <link rel="stylesheet"> elements in untrusted HTML to make Happy DOM send HTTP requests from the server to attacker-chosen URLs, including internal services. This could allow access to otherwise unreachable endpoints or trigger unintended actions, depending on the application and its network access.
    • The settings property disableCSSFileLoading has been deprecated
    • Added the new settings properties enableCSSFileLoading and enableIframePageLoading
    • If you don't believe that you are at risk, you can keep the same behavior as in <=v20.14.6 by sending in { enableCSSFileLoading: true, enableIframePageLoading: true } as broswer settings (e.g. new Window({ settings }));
Commits
  • fd16352 fix: Fixed a code injection vulnerability in the ESM compiler (#2537)
  • 75ab0fb fix: Fixed cross-origin isolation so opaque-origin data: iframes cannot acces...
  • 875ef5c fix: Fixes security vulnerability where authorization header was forwarded wh...
  • 1f3ffdf fix: Fixes SSRF security vulnerability by doing a target-origin bypass in the...
  • f55c7e0 chore: Update security documentation (#2509)
  • 2b91e68 fix: Adds alias for enabling CSS and iframe loading in server-renderer (#2503)
  • 0a99c75 BREAKING CHANGE: Disables CSS and IFrame loading by default (#2502)
  • See full diff in compare view

Updates playwright-core from 1.64.1 to 1.65.0

Release notes

Sourced from playwright-core's releases.

v1.65.0

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

  • There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
  • Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
  • Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
  • Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['failures'],
['html', { onlyFailures: true }],
],
});

🎯 Test runner

  • New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

    test('restart the server', { lock: '-exclusive-' }, async () => {
      // No other test runs while this one is running.
    });
  • test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

    test('upload a file', async ({ page }) => {
      test.skip('Not implemented yet');
    });

... (truncated)

Commits
  • a1f35e1 chore: mark v1.65.0 (#43925)
  • a99c1ab cherry-pick(#43918): Revert "fix(docker): use latest stable Chrome for Testin...
  • 6f9a7f5 cherry-pick(#43914): docs(release-notes): update Chromium version for 1.65
  • daf93bb cherry-pick(#43912): feat(chromium): roll to r1254
  • 6545e89 cherry-pick(#43902): chore(deps): bump runtime deps
  • 0347448 fix(test runner): track shared ESM dependencies for only-changed (#43837)
  • 86e6924 fix(clock): cancel real-time timer when replay ends paused (#43873)
  • d745ae0 fix(route): wait for all active handlers before disabling interception (#43889)
  • 6e3f5ff docs: release notes for v1.65 (#43874)
  • aa33d27 fix(chromium): honor Linux config directories for channel connections (#43884)
  • Additional commits viewable in compare view

Updates vitest from 5.0.4 to 5.1.0

Release notes

Sourced from vitest's releases.

v5.1.0

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

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 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

…ates

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

| Package | From | To |
| --- | --- | --- |
| [@nuxt/test-utils](https://github.com/nuxt/test-utils) | `4.3.3` | `4.3.4` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `5.0.4` | `5.1.0` |
| [happy-dom](https://github.com/capricorn86/happy-dom) | `20.14.6` | `21.0.4` |
| [playwright-core](https://github.com/microsoft/playwright) | `1.64.1` | `1.65.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.4` | `5.1.0` |



Updates `@nuxt/test-utils` from 4.3.3 to 4.3.4
- [Release notes](https://github.com/nuxt/test-utils/releases)
- [Commits](nuxt/test-utils@v4.3.3...v4.3.4)

Updates `@vitest/coverage-v8` from 5.0.4 to 5.1.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.1.0/packages/coverage-v8)

Updates `happy-dom` from 20.14.6 to 21.0.4
- [Release notes](https://github.com/capricorn86/happy-dom/releases)
- [Commits](capricorn86/happy-dom@v20.14.6...v21.0.4)

Updates `playwright-core` from 1.64.1 to 1.65.0
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.64.1...v1.65.0)

Updates `vitest` from 5.0.4 to 5.1.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.1.0/packages/vitest)

---
updated-dependencies:
- dependency-name: "@nuxt/test-utils"
  dependency-version: 4.3.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: testing
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: testing
- dependency-name: happy-dom
  dependency-version: 21.0.4
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: testing
- dependency-name: playwright-core
  dependency-version: 1.65.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: testing
- dependency-name: vitest
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: testing
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 9, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants