chore: bump devDeps (vitest/vite/esbuild patches)#9
Merged
kevinccbsg merged 2 commits intomainfrom May 8, 2026
Merged
Conversation
- @vitest/coverage-v8 ^4.1.0 → ^4.1.5 (patch) - vitest ^4.1.0 → ^4.1.5 (patch) - vite ^8.0.1 → ^8.0.11 (patch) - esbuild ^0.27.4 → ^0.28.0 (only used as `minify: 'esbuild'` mode in vite.config.ts; no direct CLI/option surface in this repo) happy-dom and typescript intentionally left untouched — happy-dom 20 is a 5-major jump and typescript 6 is a major bump, both deferred to separate PRs. Tests: 73/73 pass. Build: clean. Lockfile shrinks by 10 lines net (unused @emnapi/* transitives drop out as a side-effect of the vitest/coverage-v8 patch). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ries @rolldown/binding-wasm32-wasi@1.0.0-rc.18 (pulled in transitively by the vite/vitest bumps) declares @emnapi/core@1.10.0 and @emnapi/runtime@1.10.0 as regular deps, but npm 10 on macOS strips them from the lockfile because the parent rolldown binding is a platform-optional package. This breaks `npm ci` on Linux CI: npm error Missing: @emnapi/core@1.10.0 from lock file npm error Missing: @emnapi/runtime@1.10.0 from lock file Recover the missing entries (versions/hashes from the npm registry) so the lockfile is consistent across platforms again. `npm ci --dry-run` now succeeds locally; tests 73/73, build clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@vitest/coverage-v8^4.1.0 → ^4.1.5 (patch)vitest^4.1.0 → ^4.1.5 (patch)vite^8.0.1 → ^8.0.11 (patch)esbuild^0.27.4 → ^0.28.0 — only used here viaminify: 'esbuild'invite.config.ts:31, which is Vite's built-in mode. No esbuild CLI flags or direct API calls in this repo, so the 0.x bump has no functional surface to break.happy-domleft at^15.11.7(the 5-major jump to 20 is a separate, riskier change).typescriptleft at^5.9.3(TS 6.0 is a separate major bump).What landed in the lockfile
Net -10 lines (299 insertions / 309 deletions). esbuild platform variants flip 0.27 → 0.28; vitest/vite cascade their internal deps; two unused
@emnapi/*transitives drop out as a side-effect of the vitest+coverage-v8 patch. No phantom additions.Test plan
npm test -- --run→ 73/73 pass.npm run build→ clean (vite 8.0.11 + esbuild 0.28 tested via the build pipeline).🤖 Generated with Claude Code