Skip to content

chore: bump vite to 8.1.3#10723

Closed
hi-ogawa wants to merge 4 commits into
vitest-dev:mainfrom
hi-ogawa:chore/bump-vite-latest
Closed

chore: bump vite to 8.1.3#10723
hi-ogawa wants to merge 4 commits into
vitest-dev:mainfrom
hi-ogawa:chore/bump-vite-latest

Conversation

@hi-ogawa

@hi-ogawa hi-ogawa commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Description

Isolate whether the released Vite version jump (8.0.11 -> 8.1.3) alone causes browser-mode stacktrace column drift, independent of the SSR transform change tested in #10722

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

hi-ogawa and others added 2 commits July 7, 2026 10:44
Isolate whether the released Vite version jump (8.0.11 -> 8.1.3) alone
causes browser-mode stacktrace column drift, independent of the SSR
transform change in vitejs/vite#22829.

Co-authored-by: OpenCode (claude-opus-4-8) <[email protected]>
@netlify

netlify Bot commented Jul 7, 2026

Copy link
Copy Markdown

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit c8703aa
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6a4c5a7aec670a00088dabb8
😎 Deploy Preview https://deploy-preview-10723--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

hi-ogawa and others added 2 commits July 7, 2026 11:45
rolldown/oxc sourcemaps in vite 8.1.3 (rolldown 1.1.4) now anchor the
failing call frame at the opening `(`, matching the non-rolldown/esbuild
output. This only affects webkit (JSC), so the `webkit && rolldownVersion`
snapshot arms now equal the non-rolldown arms; collapse them and drop the
unused `rolldownVersion` import.

Co-authored-by: OpenCode (claude-opus-4-8) <[email protected]>
Same rolldown/oxc sourcemap convergence as the other webkit stacktrace
snapshots: the `if (rolldownVersion)` webkit frames now match the
non-rolldown branch, so collapse the branches and drop the unused
`rolldownVersion` import.

Co-authored-by: OpenCode (claude-opus-4-8) <[email protected]>
Comment on lines 166 to -168
if (name === 'webkit') {
if (rolldownVersion) {
expect(tree).toMatchInlineSnapshot(`

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like technically stack trace (source map) regressed for webkit. Should flag it to Vite / Oxc though may be edge case.

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.

1 participant