build(deps-dev): bump @vitejs/plugin-react from 4.7.0 to 6.0.4 in /ui

[dependabot]

Bumps @vitejs/plugin-react from 4.7.0 to 6.0.4.

Release notes

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

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'],



}),

]
})

For React compiler users, you can use reactCompilerPreset for easier setup with preconfigured filter to improve build performance:

 import { defineConfig } from 'vite'
</tr></table> 

... (truncated)

Changelog

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

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: {



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



  },



}),





react(),



babel({



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



</tr></table>

... (truncated)

Commits

• 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)
• 6c57dd4 fix(plugin-react): use '/' base in bundledDev preamble to fix non-root base p...
• 3cc33a7 fix(deps): update react-related dependencies (#1245)
• c0f7c7f docs: mention the Biome rule in the "Consistent components exports" section (...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​vitejs/plugin-react since your current version.

[Chris-ObtuseAI]

Not landable as a dependency bump — this is a hidden two-major Vite migration

npm error While resolving: @vitejs/plugin-react@6.0.4
npm error Found: vite@6.4.3
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.0.4
npm error Conflicting peer dependency: vite@8.2.0

The plugin requires Vite 8; this repo is on Vite 6.4.3. Dependabot bumped the plugin without its peer, so npm ci cannot resolve and Organism UI, Build synthetic-only Organism and the Windows validation all fail at install.

This cannot be fixed by updating a lock file. The options are:

1. A grouped upgrade that moves vite 6 -> 8 and @vitejs/plugin-react together, with the UI suite and Playwright smoke re-run against it.
2. Leave the plugin on 4.x until a Vite major upgrade is scheduled on its own merits.

What should not happen: --legacy-peer-deps or --force. npm says it plainly — that accepts "an incorrect (and potentially broken) dependency resolution", and the UI smoke tests already exercise a real browser against a dev server, so a broken resolution would surface as a confusing runtime failure rather than an install error.

Diagnosed 2026-08-02 while triaging the three open dependabot PRs. They are three different problems: #16 is a genuine pin-site job (a version is pinned in five places, dependabot updates two), #36 is a breaking Rust API change (Hmac::new_from_slice removed, Array no longer implements LowerHex), and this one is a major migration.

[dependabot]

Superseded by #72.