Skip to content

chore(deps): update stable dependencies across WebGPU packages - #55

Merged
sebavan merged 1 commit into
mainfrom
chore/update-stable-dependencies
Nov 10, 2026
Merged

sebavan merged 1 commit into
mainfrom
chore/update-stable-dependencies

Conversation

@sebavan

@sebavan sebavan commented Nov 10, 2026

Copy link
Copy Markdown
Owner

What changed

  • Refresh stable dependencies and npm lockfiles in the root, MCP server, and capture CLI skill, including supported major upgrades.
  • Upgrade jsdom 29 -> 31 and the independent MCP compiler from TypeScript 6 -> 7.
  • Update Babylon.js to 9.35.0, Playwright across all three packages to 1.65.0, Vitest/coverage to 5.1.0, typescript-eslint to 8.72.2, ESLint to 10.14.0, webpack-cli to 7.3.1, Sass to 1.108.1, globals to 17.14.0, rimraf to 6.1.4, and MCP Node types to 26.6.6.
  • Migrate the capture benchmark from Vitest's removed top-level bench export to the test-context fixture.
  • Document the root TypeScript exception: latest stable typescript-eslint requires typescript >=4.8.4 <6.1.0. Installing TypeScript 7 fails with ERESOLVE, so retain 6.0.3 without bypassing peer checks. npm outdated reports only this intentional root exception; both nested packages have no outdated direct dependencies.
  • No application API, capture format, browser permission, or interception/readback source changes.

Validation

Windows, Node v24.22.2, npm 11.19.1. Clean installs were verified in all three packages.

Passed:

  • Root: npm ci; npm test (354 tests / 25 files); npm run lint; npm run check:versions; npx tsc --noEmit; npm run build.
  • Root: npm run bench:capture and npm run bench:capture -- --reporter=verbose (one benchmark test). Verbose mean: 9.4207 ms per 10,000 commands, 107 samples, +/-1.43% RME. Vitest warns about module-export getter overhead; this is not GPU readback or release qualification.
  • MCP: npm ci; npm test (90 tests / 2 files); npm run build using TypeScript 7.
  • Capture CLI skill: npm ci; node --check capture-cli.js; node --check summary.js.
  • All three packages: npm audit --audit-level=high passes. MCP and skill report zero vulnerabilities; root reports nine moderate findings through development-only minimatch dependencies. The available audit remedy downgrades ESLint/typescript-eslint across majors; no forced downgrade or unsupported minimatch override was applied.
  • git diff --check and manifest/lock dependency metadata consistency checks.

Failed / environment limits (not claimed as passing):

  • npm run test:e2e -- --retries=0: 3 passed, 8 failed, 11 did not run across all 22 tests. Executed headed with official Chrome for Testing stable 157.0.8103.50 after npx playwright install chrome failed to install system Chrome. Local WebGPU fixtures report NO_ADAPTER; Babylon Playground device discovery times out; webgpu-samples reports WebGPU not detected; the compute result test times out. Both no-WebGPU extension smoke tests and the compute-page error check pass. A GPU-enabled environment is still required to validate capture/coexistence end to end. No test expectations or skips were weakened. The temporary Chrome path junction was removed afterward.
  • npm run test:coverage: all 354 tests pass, but global 60% thresholds fail: statements 52.47%, branches 44.11%, functions 57.17%, lines 54.38%. Thresholds were not lowered.
  • Production build passes with webpack bundle/entrypoint size and runtime-chunk recommendation warnings. jsdom reports unsupported canvas getContext calls during unit tests.

Impact

  • Capture format or public API
  • Browser permissions or privacy
  • Performance-sensitive interception/readback path
  • Result-viewer UI
  • MCP tools
  • Documentation only

Checklist

  • Tests cover the changed behavior
  • Relevant specs and public documentation are updated
  • CHANGELOG.md is updated for a notable user-facing change
  • UI changes include a screenshot or recording
  • No generated build output, reports, secrets, or proprietary capture data are included

Changelog and screenshots are not applicable: this dependency/toolchain refresh does not intentionally change user-facing behavior or UI layout.

Upgrade supported major releases, migrate the Vitest benchmark API, and document the root TypeScript peer compatibility constraint.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@sebavan
sebavan merged commit 6752adf into main Nov 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants