build(deps-dev): Bump vite from 7.3.6 to 8.1.3 in /frontend#4
Closed
dependabot[bot] wants to merge 1 commit into
Closed
build(deps-dev): Bump vite from 7.3.6 to 8.1.3 in /frontend#4dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.3.6 to 8.1.3. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.1.3/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.1.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
xeri
added a commit
that referenced
this pull request
Jul 14, 2026
Dependabot opened these as three PRs (#4, #5, #2). They cannot land that way: @vitejs/plugin-react@6 peer-requires vite@^8, so #5's npm ci fails against a tree that still has vite 7, and typescript@6 fails on our tsconfig regardless of the other two. Bumped together, they resolve cleanly. TypeScript 6 promotes two long-deprecated options to hard errors (TS5107): esModuleInterop: false -> true. allowSyntheticDefaultImports was already on and is implied by esModuleInterop, so it goes; noEmit means this only ever affected type-checking, never the shipped bundle (vite does the transform). moduleResolution: Node (node10) -> bundler, which is what a Vite project has actually been doing all along; node10 was describing a resolver we don't use. The ignoreDeprecations escape hatch would have bought silence until TS 7 and no more, so it is not worth taking. vite 8 swaps the bundler to Rolldown, which regenerates the production chunk with entirely different codegen — a green build does not prove that renders. Verified: tsc + vite build clean; all 7 devmock scenarios x 7 screens with zero page errors; the Rolldown production bundle mounts React with zero errors under a stubbed Wails runtime; wails build green with no frontend/wailsjs churn; full Go suite green. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Owner
|
Superseded by #7, which lands |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
xeri
added a commit
that referenced
this pull request
Jul 16, 2026
Dependabot opened these as three PRs (#4, #5, #2). They cannot land that way: @vitejs/plugin-react@6 peer-requires vite@^8, so #5's npm ci fails against a tree that still has vite 7, and typescript@6 fails on our tsconfig regardless of the other two. Bumped together, they resolve cleanly. TypeScript 6 promotes two long-deprecated options to hard errors (TS5107): esModuleInterop: false -> true. allowSyntheticDefaultImports was already on and is implied by esModuleInterop, so it goes; noEmit means this only ever affected type-checking, never the shipped bundle (vite does the transform). moduleResolution: Node (node10) -> bundler, which is what a Vite project has actually been doing all along; node10 was describing a resolver we don't use. The ignoreDeprecations escape hatch would have bought silence until TS 7 and no more, so it is not worth taking. vite 8 swaps the bundler to Rolldown, which regenerates the production chunk with entirely different codegen — a green build does not prove that renders. Verified: tsc + vite build clean; all 7 devmock scenarios x 7 screens with zero page errors; the Rolldown production bundle mounts React with zero errors under a stubbed Wails runtime; wails build green with no frontend/wailsjs churn; full Go suite green. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
xeri
added a commit
that referenced
this pull request
Jul 16, 2026
Dependabot opened these as three PRs (#4, #5, #2). They cannot land that way: @vitejs/plugin-react@6 peer-requires vite@^8, so #5's npm ci fails against a tree that still has vite 7, and typescript@6 fails on our tsconfig regardless of the other two. Bumped together, they resolve cleanly. TypeScript 6 promotes two long-deprecated options to hard errors (TS5107): esModuleInterop: false -> true. allowSyntheticDefaultImports was already on and is implied by esModuleInterop, so it goes; noEmit means this only ever affected type-checking, never the shipped bundle (vite does the transform). moduleResolution: Node (node10) -> bundler, which is what a Vite project has actually been doing all along; node10 was describing a resolver we don't use. The ignoreDeprecations escape hatch would have bought silence until TS 7 and no more, so it is not worth taking. vite 8 swaps the bundler to Rolldown, which regenerates the production chunk with entirely different codegen — a green build does not prove that renders. Verified: tsc + vite build clean; all 7 devmock scenarios x 7 screens with zero page errors; the Rolldown production bundle mounts React with zero errors under a stubbed Wails runtime; wails build green with no frontend/wailsjs churn; full Go suite green.
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.
Bumps vite from 7.3.6 to 8.1.3.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
578ffb8release: v8.1.37103c3afix(deps): bumpes-module-lexerto 2.3.0 (#22838)1534d36fix(css): inject inlined CSS after the shebang line (#22717)c4acd69fix(ssr): correct stacktrace column position for first line (#22828)2c53054fix: preload css for nested dynamic imports (#22759)ba31193release: v8.1.20d3bd7cfix(deps): revert es-module-lexer to 2.1.0 (#22827)efb98ccfix: restore, "fix: resolve pnpm .modules.yaml from workspace root instead of...cf97711fix: revert, "fix: resolve pnpm .modules.yaml from workspace root instead of ...cccef55fix: revert, "fix: escape ids with multiple null bytes (#22687)"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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)