Skip to content

build(deps): bump the npm group with 4 updates - #5

Merged
jchrist merged 3 commits into
mainfrom
dependabot/npm_and_yarn/npm-3daba76e3c
Oct 12, 2026
Merged

jchrist merged 3 commits into
mainfrom
dependabot/npm_and_yarn/npm-3daba76e3c

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 12, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm group with 4 updates: @voidzero-dev/vite-plus-core, @playwright/test, jsdom and vite-plus.

Updates @voidzero-dev/vite-plus-core from 1.0.0 to 1.1.0

Release notes

Sourced from @​voidzero-dev/vite-plus-core's releases.

vite-plus v1.1.0: faster vp dev startup and clearer interactive prompts

Vite+ 1.1 starts vp dev faster and makes the interactive prompts clearer, alongside fixes for vp migrate, package-manager commands, and Windows terminals.

Highlights

  • vp dev reaches its local URL about 24% sooner and uses about 30% less memory in the parent process, because Vite+ no longer loads Vite and Vitest there before starting the dev server (#2851), by @​camc314.
  • Interactive prompts render boxes, logs, and wrapped text consistently, with clearer hints, validation, and navigation instructions (#2870), by @​cpojer.

Features

  • vp run sets npm_execpath and npm_config_user_agent for npm, pnpm, and Yarn, so tools such as npm-run-all2 use the project's package manager instead of falling back to npm (#2895), by @​naokihaba and @​tarikermis.
  • Upgrade vite@8.3.1 to vite@8.3.3, rolldown@1.2.11 to rolldown@1.2.12, vitest@5.0.1 to vitest@5.0.3, oxlint@1.85.0 to oxlint@1.87.0, and oxfmt@0.70.0 to oxfmt@0.72.0. The new lint and format versions can flag code that passed before, so run vp fmt after upgrading if CI runs vp check. vp migrate now keeps the React Refresh allowCompoundComponents option because the bundled Oxlint supports it (#2871, #2896, #2904), by @​voidzero-guard[bot].

Fixes & Enhancements

  • vp migrate keeps Oxlint rules written with plugin aliases (such as @typescript-eslint/*, react-hooks/*, and import-x/*) and removes rules the bundled Oxlint does not support, listing them in a warning (#2820, #2906), by @​TheAlexLichter and @​yusuke99.
  • vp migrate leaves projects without a declared package manager unpinned, keeps existing declarations, and points to vp env pin when it infers one (#2817), by @​TheAlexLichter.
  • vp migrate reports a short error for a directory without package.json instead of an ENOENT stack trace (#2821), by @​TheAlexLichter.
  • vp create in an existing pnpm workspace adds the catalog entries the new application needs, so installation no longer fails with ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC (#2808), by @​SaKaNa-Y.
  • On Windows, one Ctrl+C stops vpr scripts and managed Bun, pnpm, npm, and Yarn commands without leaving cmd.exe stuck at Terminate batch job (Y/N)? (#2890), by @​fengmk2.
  • vp pack --watch on Windows rebuilds with the new options after the config file changes (#2826), by @​liangmiQwQ.
  • vp test doctor and vp test complete run the Vitest subcommands instead of being treated as test file filters (#2879), by @​liangmiQwQ.
  • With isolated dependency layouts such as pnpm's global virtual store, vp pack finds installed Vue language tools and TypeScript Go for declaration generation, and Playwright browser provider options keep their types (#2868, #2865), by @​liangmiQwQ.
  • Package-manager commands fail when the project's package manager does not support a named option, instead of silently dropping it and continuing. Bun 1.4.1+ receives --offline and --prefer-offline, and Yarn Classic accepts a single --filter for vp remove (#2775), by @​jong-kyung.
  • vp pm config in Bun projects falls back to npm, as its warning says (#2899), by @​jong-kyung.
  • vp pm approve-builds states that Yarn Berry disables third-party build scripts by default from 4.14.0, not in every version (#2902), by @​jong-kyung.
  • vp implode asks you to type boom instead of uninstall to confirm (#2901), by @​fengmk2.
  • Global package installs and updates print a green +, and removals a red -, with bold package names in both (#2828), by @​liangmiQwQ.
  • Setup headings and command hints keep their colors when the installer captures stdout (#2829), by @​liangmiQwQ.

Refactor

  • Replace semver with verkit in the CLI, reducing the bundled CLI JavaScript by about 26 KB (#2837), by @​liangmiQwQ.
  • Share the shim filename logic between setup and vp env doctor, and remove unused config migration metadata (#2876, #2894), by @​jong-kyung.

Docs

  • Announce Vite+ 1.0 on the website and update the homepage vp pack demo (#2843, #2844), by @​TheAlexLichter and @​naokihaba.
  • Document vp install -g --node and explain when vp env default re-resolves versions (#2885, #2884), by @​hyunbinseo.
  • Use runnable package examples in the vpx guide and vpx --help (#2864), by @​SaKaNa-Y.
  • Remove the redundant vp install step from setup-vp CI examples (#2888), by @​yusuke99.
  • Explain how to return from a preview build, align manual installation examples with the installed toolchain, and update the JetBrains Node.js path and vp env current --json example for the split directory layout (#2886, #2887, #2889, #2891), by @​jong-kyung.

Chore

... (truncated)

Commits
  • 3aa366e release: v1.1.0: faster vp dev startup and clearer interactive prompts (#2907)
  • f978fdc feat(deps): upgrade upstream dependencies (#2904)
  • 36406f7 fix(core): declare optional peers of bundled rolldown-plugin-dts (#2868)
  • 361eba5 feat(deps): upgrade upstream dependencies (#2871)
  • See full diff in compare view

Updates @playwright/test from 1.63.0 to 1.64.0

Release notes

Sourced from @​playwright/test's releases.

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
highlight: 'outline: 2px solid #333; background: rgba(0, 128, 255, .15)',
title: 'font-size: 16px',
},
},
},
},
</tr></table>

... (truncated)

Commits
  • 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
  • e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
  • f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
  • e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
  • d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
  • a0c4b5e cherry-pick(#43175): feat(api): return language-specific locator code from re...
  • 3f7d535 cherry-pick(#43131): docs: fix broken C# samples in API docs and handles guide
  • 1cde64f cherry-pick(#43170): fix(locators): parse mixed role options
  • 8851e72 cherry-pick(#43171): fix(locators): parse JavaScript escapes and regex classes
  • dcc5065 cherry-pick(#43172): fix(locator): parse within and getByRef locators
  • Additional commits viewable in compare view

Updates jsdom from 30.1.1 to 30.1.2

Release notes

Sourced from jsdom's releases.

v30.1.2

  • Updated URLs to support Unicode v18.0.0 in internationalized domain names.
  • Reduced package size and memory use for CSS property definitions. (@​scttcper)
  • Fixed severe slowdowns when building large DOM trees, including SVG charts with D3, which regressed in v30.1.0. (@​cmdcolin)
  • Fixed exponentially slow reads of empty inherited CSS custom properties in deeply nested documents, and custom properties incorrectly inheriting past an initial reset. (@​scttcper)
  • Fixed getComputedStyle() returning stale results after editing stylesheet declarations, selectors, or media queries, including in imported stylesheets.
  • Fixed selector matching and computed styles after changes to form control checkedness, indeterminacy, selection, values, and validity, including during form resets and canceled clicks.
  • Fixed computed styles for :focus, :focus-visible, :focus-within, and selectors containing them after focus changes, including inside focus and blur listeners. (@​asamuzaK)
  • Fixed element.focus() incorrectly focusing elements hidden by 'display', including through shadow hosts and slots, and elements excluded by shadow DOM slot assignment. (@​asamuzaK)
  • Fixed getComputedStyle() throwing for elements without inline-style support, including XML and MathML elements.
  • Fixed a memory leak where stylesheet parsing retained the last parsed stylesheet's window after window.close().
  • Fixed memory growth from long-lived MutationObserver instances retaining bookkeeping for garbage-collected nodes. (@​scttcper)
  • Fixed retained select.selectedOptions collections becoming stale after selection changes and form resets.
  • Fixed rejection of negative CSS sizing values, including for 'min-width', 'min-height', 'max-width', and 'max-height', which regressed in v30.1.0.
  • Fixed handling of deeply nested color-mix() expressions, including exceptions during color resolution. (@​asamuzaK)
Commits
  • a23bfb7 30.1.2
  • 64a75d2 Update dependencies and dev dependencies
  • 7bf9653 Invalidate styles after CSSOM and control state changes
  • fe9009c Update focused area handling
  • a8d28b3 Release windows retained by stylesheet parsing
  • 05a2c01 Deduplicate generated CSS property metadata
  • 1efa190 Reduce generated CSS property data
  • a372e12 Avoid Document named-property rebuilds after irrelevant tree mutations
  • b2cd235 Update css-color
  • 0542d2b Release idle MutationObserver bookkeeping
  • Additional commits viewable in compare view

Updates vite-plus from 1.0.0 to 1.1.0

Release notes

Sourced from vite-plus's releases.

vite-plus v1.1.0: faster vp dev startup and clearer interactive prompts

Vite+ 1.1 starts vp dev faster and makes the interactive prompts clearer, alongside fixes for vp migrate, package-manager commands, and Windows terminals.

Highlights

  • vp dev reaches its local URL about 24% sooner and uses about 30% less memory in the parent process, because Vite+ no longer loads Vite and Vitest there before starting the dev server (#2851), by @​camc314.
  • Interactive prompts render boxes, logs, and wrapped text consistently, with clearer hints, validation, and navigation instructions (#2870), by @​cpojer.

Features

  • vp run sets npm_execpath and npm_config_user_agent for npm, pnpm, and Yarn, so tools such as npm-run-all2 use the project's package manager instead of falling back to npm (#2895), by @​naokihaba and @​tarikermis.
  • Upgrade vite@8.3.1 to vite@8.3.3, rolldown@1.2.11 to rolldown@1.2.12, vitest@5.0.1 to vitest@5.0.3, oxlint@1.85.0 to oxlint@1.87.0, and oxfmt@0.70.0 to oxfmt@0.72.0. The new lint and format versions can flag code that passed before, so run vp fmt after upgrading if CI runs vp check. vp migrate now keeps the React Refresh allowCompoundComponents option because the bundled Oxlint supports it (#2871, #2896, #2904), by @​voidzero-guard[bot].

Fixes & Enhancements

  • vp migrate keeps Oxlint rules written with plugin aliases (such as @typescript-eslint/*, react-hooks/*, and import-x/*) and removes rules the bundled Oxlint does not support, listing them in a warning (#2820, #2906), by @​TheAlexLichter and @​yusuke99.
  • vp migrate leaves projects without a declared package manager unpinned, keeps existing declarations, and points to vp env pin when it infers one (#2817), by @​TheAlexLichter.
  • vp migrate reports a short error for a directory without package.json instead of an ENOENT stack trace (#2821), by @​TheAlexLichter.
  • vp create in an existing pnpm workspace adds the catalog entries the new application needs, so installation no longer fails with ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC (#2808), by @​SaKaNa-Y.
  • On Windows, one Ctrl+C stops vpr scripts and managed Bun, pnpm, npm, and Yarn commands without leaving cmd.exe stuck at Terminate batch job (Y/N)? (#2890), by @​fengmk2.
  • vp pack --watch on Windows rebuilds with the new options after the config file changes (#2826), by @​liangmiQwQ.
  • vp test doctor and vp test complete run the Vitest subcommands instead of being treated as test file filters (#2879), by @​liangmiQwQ.
  • With isolated dependency layouts such as pnpm's global virtual store, vp pack finds installed Vue language tools and TypeScript Go for declaration generation, and Playwright browser provider options keep their types (#2868, #2865), by @​liangmiQwQ.
  • Package-manager commands fail when the project's package manager does not support a named option, instead of silently dropping it and continuing. Bun 1.4.1+ receives --offline and --prefer-offline, and Yarn Classic accepts a single --filter for vp remove (#2775), by @​jong-kyung.
  • vp pm config in Bun projects falls back to npm, as its warning says (#2899), by @​jong-kyung.
  • vp pm approve-builds states that Yarn Berry disables third-party build scripts by default from 4.14.0, not in every version (#2902), by @​jong-kyung.
  • vp implode asks you to type boom instead of uninstall to confirm (#2901), by @​fengmk2.
  • Global package installs and updates print a green +, and removals a red -, with bold package names in both (#2828), by @​liangmiQwQ.
  • Setup headings and command hints keep their colors when the installer captures stdout (#2829), by @​liangmiQwQ.

Refactor

  • Replace semver with verkit in the CLI, reducing the bundled CLI JavaScript by about 26 KB (#2837), by @​liangmiQwQ.
  • Share the shim filename logic between setup and vp env doctor, and remove unused config migration metadata (#2876, #2894), by @​jong-kyung.

Docs

  • Announce Vite+ 1.0 on the website and update the homepage vp pack demo (#2843, #2844), by @​TheAlexLichter and @​naokihaba.
  • Document vp install -g --node and explain when vp env default re-resolves versions (#2885, #2884), by @​hyunbinseo.
  • Use runnable package examples in the vpx guide and vpx --help (#2864), by @​SaKaNa-Y.
  • Remove the redundant vp install step from setup-vp CI examples (#2888), by @​yusuke99.
  • Explain how to return from a preview build, align manual installation examples with the installed toolchain, and update the JetBrains Node.js path and vp env current --json example for the split directory layout (#2886, #2887, #2889, #2891), by @​jong-kyung.

Chore

... (truncated)

Commits
  • 3aa366e release: v1.1.0: faster vp dev startup and clearer interactive prompts (#2907)
  • b639509 fix(shim): preserve Windows terminal after Ctrl+C (#2890)
  • 390f215 perf(cli): defer Vite config resolver until needed (#2851)
  • 27b4ffd fix(migrate): strip unsupported Oxlint rules with report (#2906)
  • 7944376 fix(create): complete catalogs in existing pnpm workspaces (#2808)
  • 6961386 fix(migrate): preserve unpinned package manager policy (#2817)
  • d0490f6 fix(migrate): preserve Oxlint rule aliases (#2820)
  • 1ebe40a fix(migrate): report missing package.json (#2821)
  • 64cc3aa fix(cli): reload pack config on Windows in watch mode (#2826)
  • c03dd22 fix(cli): set package-manager lifecycle env for vp run (#2895)
  • Additional commits viewable 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 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

Bumps the npm group with 4 updates: [@voidzero-dev/vite-plus-core](https://github.com/voidzero-dev/vite-plus/tree/HEAD/packages/core), [@playwright/test](https://github.com/microsoft/playwright), [jsdom](https://github.com/jsdom/jsdom) and [vite-plus](https://github.com/voidzero-dev/vite-plus/tree/HEAD/packages/cli).


Updates `@voidzero-dev/vite-plus-core` from 1.0.0 to 1.1.0
- [Release notes](https://github.com/voidzero-dev/vite-plus/releases)
- [Commits](https://github.com/voidzero-dev/vite-plus/commits/v1.1.0/packages/core)

Updates `@playwright/test` from 1.63.0 to 1.64.0
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.63.0...v1.64.0)

Updates `jsdom` from 30.1.1 to 30.1.2
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Commits](jsdom/jsdom@v30.1.1...v30.1.2)

Updates `vite-plus` from 1.0.0 to 1.1.0
- [Release notes](https://github.com/voidzero-dev/vite-plus/releases)
- [Commits](https://github.com/voidzero-dev/vite-plus/commits/v1.1.0/packages/cli)

---
updated-dependencies:
- dependency-name: "@voidzero-dev/vite-plus-core"
  dependency-version: 1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm
- dependency-name: "@playwright/test"
  dependency-version: 1.64.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm
- dependency-name: jsdom
  dependency-version: 30.1.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm
- dependency-name: vite-plus
  dependency-version: 1.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm
...

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 Oct 12, 2026
Dependabot bumped vite-plus-core and vite-plus to 1.1.0 but left the
vite npm-alias and overrides on 1.0.0 and vitest on 5.0.1. vp refuses
to run with a mismatched alias (Expected 1.1.0, found 1.0.0), so every
CI job failed at compile. Bump the alias, overrides, and vitest to the
versions vite-plus 1.1.0 pins (5.0.3), and move the dependabot vitest
ignore one patch ahead.
Enable squash auto-merge for PRs authored by dependabot[bot] via
pull_request_target, so grouped bumps land as one linear commit the
moment the five required checks pass. See workflow comments for the
safety notes (no checkout, squash for linear history).
@jchrist
jchrist enabled auto-merge (squash) October 12, 2026 20:49
@jchrist
jchrist merged commit 1c18536 into main Oct 12, 2026
6 checks passed
@jchrist
jchrist deleted the dependabot/npm_and_yarn/npm-3daba76e3c branch October 12, 2026 20:51
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.

1 participant