chore(web)(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.0.5 in /web

[dependabot]

Bumps @vitejs/plugin-react from 5.2.0 to 6.0.5.

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.0.5

Fixed the react compiler preset filter to be linear (#1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#1349). The filter was changed to be linear to avoid that.

plugin-react@6.0.4

Fixed $RefreshSig$ is not defined error when running vite dev with NODE_ENV=production

When running vite dev with NODE_ENV=production, the app errored with $RefreshSig$ is not defined. This error is now fixed.

plugin-react@6.0.3

No release notes provided.

plugin-react@6.0.2

Allow all options in reactCompilerPreset (#1189)

This is a type only change. Only compilationMode and target options were available for reactCompilerPreset.

plugin-react@6.0.1

Expand @rolldown/plugin-babel peer dep range (#1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

plugin-react@6.0.0

Remove Babel Related Features (#1123)

Vite 8+ can handle React Refresh Transform by Oxc and doesn't need Babel for it. With that, there are no transform applied that requires Babel. To reduce the installation size of this plugin, babel is no longer a dependency of this plugin and the related features are removed.

If you are using Babel, you can use @rolldown/plugin-babel together with this plugin:

 import { defineConfig } from 'vite'
 import react from '@vitejs/plugin-react'
+import babel from '@rolldown/plugin-babel'
export default defineConfig({
plugins: [


react({



  babel: {



    plugins: ['@babel/plugin-proposal-throw-expressions'],



  },



}),





react(),



babel({



  plugins: ['@babel/plugin-proposal-throw-expressions'],



}),

]
})

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.0.5 (2026-07-30)

Fixed the react compiler preset filter to be linear (#1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#1349). The filter was changed to be linear to avoid that.

6.0.4 (2026-07-22)

Fixed $RefreshSig$ is not defined error when running vite dev with NODE_ENV=production

When running vite dev with NODE_ENV=production, the app errored with $RefreshSig$ is not defined. This error is now fixed.

6.0.3 (2026-06-23)

Improve the react compiler preset filter to reduce false-positives (#1138)

Improved the filter in the react compiler babel preset to reduce the false-positives so that less modules are processed by the react compiler.

6.0.2 (2026-05-14)

Allow all options in reactCompilerPreset (#1189)

This is a type only change. Only compilationMode and target options were available for reactCompilerPreset.

6.0.1 (2026-03-13)

Expand @rolldown/plugin-babel peer dep range (#1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

6.0.0 (2026-03-12)

6.0.0-beta.0 (2026-03-03)

Remove Babel Related Features (#1123)

Vite 8+ can handle React Refresh Transform by Oxc and doesn't need Babel for it. With that, there are no transform applied that requires Babel. To reduce the installation size of this plugin, babel is no longer a dependency of this plugin and the related features are removed.

If you are using Babel, you can use @rolldown/plugin-babel together with this plugin:

 import { defineConfig } from 'vite'
 import react from '@vitejs/plugin-react'
+import babel from '@rolldown/plugin-babel'
export default defineConfig({
plugins: [


react({



  babel: {



</tr></table>

... (truncated)

Commits

• 68c0cb8 release: plugin-react@6.0.5 (#1362)
• 555cdbc fix(react): make the react compiler preset filter linear (#1353)
• a00a9f8 fix(deps): update all non-major dependencies (#1327)
• f4b5498 release: plugin-react@6.0.4
• 7a40659 fix(react): $RefreshSig$ is not defined with NODE_ENV=production vite dev ...
• 98b32d4 fix(deps): update react 19.2.8 (#1298)
• 8ae5449 fix: babel-plugin-react-compiler cannot be imported when used in a framework ...
• f09ea01 fix(deps): update all non-major dependencies (#1282)
• 640fd35 release: plugin-react@6.0.3
• 889efb0 fix(deps): update all non-major dependencies (#1249)
• Additional commits viewable in compare view

[engrams-agent]

✅ engrams review — complete. 0 findings posted. · View details

[engrams-agent]

Engrams review

Verdict: No findings.
Severity: Critical 0 · High 0 · Medium 0 · Low 0

View the full engrams review

[engrams-agent]

✅ engrams review — complete. 0 findings posted. · View details

[engrams-agent]

Engrams review

Verdict: No findings.
Severity: Critical 0 · High 0 · Medium 0 · Low 0

View the full engrams review

[engrams-agent]

✅ engrams review — complete. 0 findings posted. · View details

[engrams-agent]

Engrams review

Verdict: No findings.
Severity: Critical 0 · High 0 · Medium 0 · Low 0

View the full engrams review

[engrams-agent]

✅ engrams review — complete. 0 findings posted. · View details

[engrams-agent]

Engrams review

Verdict: No findings.
Severity: Critical 0 · High 0 · Medium 0 · Low 0

View the full engrams review

[engrams-agent]

Reviewed — green, and no source change is needed

Picked this up in today's dependency sweep. It is a major bump, so here is the
breaking surface and what I verified.

What upstream changed

All the breaking changes are in 6.0.0; 6.0.1–6.0.5 are fixes.

1. Babel is gone (#1123).
   Vite 8 applies the React Refresh transform with Oxc, so the plugin no longer
   needs Babel. The react({ babel: { … } }) option was removed, and
   @babel/core + react-refresh are no longer dependencies. Consumers who
   need Babel now compose @rolldown/plugin-babel themselves.
2. Vite 7 and below are unsupported (#1124).
   The peer range narrows from ^4.2.0 || ^5 || ^6 || ^7 || ^8 to ^8.0.0.
3. The classic-runtime React auto-import was dropped, and react/react-dom
   are no longer added to resolve.dedupe automatically.

Note what did not change: engines stays ^20.19.0 || >=22.12.0. That is
why this PR is green while #940 (jsdom 30) is red — jsdom raised its Node floor,
this plugin did not.

Why none of it touches us

• web/vite.config.ts calls react() with no options at all, so there is
  no babel key to migrate and no reactCompiler config.
• web/package.json already pins vite: ^8.2.0, which satisfies the new
  ^8.0.0 peer.
• There is no .babelrc, no babel.config.*, no direct @babel/* dependency,
  and no resolve.dedupe anywhere in web/.
• pnpm-lock.yaml resolves a single react@19.2.8 / react-dom@19.2.8, so
  losing the automatic dedupe is a no-op — there is no duplicate copy to dedupe.
• web/index.html is a plain SPA shell with no manual React Refresh preamble,
  so nothing imports @vitejs/plugin-react/preamble.

The lockfile diff is purely subtractive on the Babel side: @babel/core,
parser, traverse, types, template, generator, compat-data, the
helper-* set, both plugin-transform-react-jsx-*, the @types/babel__* set
and react-refresh all drop out. That is ~20 fewer transitive packages in the
web install, which shortens pnpm install for every other web PR.

What I verified

The green web (pnpm) check on this branch ran against a base that is now 5
commits behind main, and main has changed 28 files under web/ since —
including the session work-pane rebuild in #1041. A stale green is not evidence
about the merged tree, so I merged current main into this branch locally and
re-ran the whole web lane:

pnpm format:check   All matched files use the correct format. (290 files)
pnpm lint (oxlint)  clean
pnpm build          tsc -b + vite build — clean
pnpm test           Test Files 54 passed (54)
                    Tests     409 passed (409)

No edits were required to get there. Merging as-is; the merge queue re-runs CI
on the merged commit, so the combined state is checked again before it lands.

What a reviewer should look at closely

Fast Refresh is the one behaviour no check covers. The web lane runs
install → format → lint → build → test and never boots vite dev. v6 is
exactly where the refresh transform moved from Babel to Oxc, so if anything
regressed it would show up only in the dev server. If you touch the frontend
soon, edit a component under just dev and confirm HMR swaps it without a full
reload and without losing component state. Low risk — this is the plugin's
headline supported path on Vite 8, and 6.0.4 already fixed the one reported
refresh bug ($RefreshSig$ is not defined under NODE_ENV=production), which
this bump includes.