build(deps-dev): Bump @vitejs/plugin-react from 5.2.0 to 6.0.3 in /frontend#5
Conversation
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 5.2.0 to 6.0.3. - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.3/packages/plugin-react) --- updated-dependencies: - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
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>
|
Superseded by #7, which lands |
|
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. |
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>
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.
Bumps @vitejs/plugin-react from 5.2.0 to 6.0.3.
Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
640fd35release: plugin-react@6.0.3889efb0fix(deps): update all non-major dependencies (#1249)6c57dd4fix(plugin-react): use '/' base in bundledDev preamble to fix non-root base p...3cc33a7fix(deps): update react-related dependencies (#1245)c0f7c7fdocs: mention the Biome rule in the "Consistent components exports" section (...cd80f0ffix(deps): update all non-major dependencies (#1241)e38accafix(deps): update all non-major dependencies (#1227)9a9bb26perf(react): improve react compiler preset so that slightly more modules are ...6535b55release: plugin-react@6.0.2bf0e43bfeat(react): whitelist debugging-options (#1189)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)