v6 rejects React Fast Refresh for files that export both a React component and a static configuration object

[Artur-]

Related plugins

• plugin-react

• plugin-react-swc

• plugin-rsc

Describe the bug

@vitejs/plugin-react v6 rejects React Fast Refresh for files that export both a React component and a static configuration object. Instead of hot-updating the component, the module is invalidated and a full page reload occurs.

This worked in v5 — the same file patterns were hot-refreshed without issues.

Reproduction

https://github.com/Artur-/vite-hmr-config-repro

Steps to reproduce

npm install
npx vite

1. Open http://localhost:5173
2. Click "Increment" a few times to set count > 0
3. touch src/HelloView.tsx
4. Observe that count resets to 0 (full reload instead of HMR)
5. Vite outputs

4:08:22 PM [vite] (client) hmr invalidate /src/HelloView.tsx Could not Fast Refresh ("config" export is incompatible). Learn more at https://github.com/vitejs/vite-plugin-react/tree/main/packages/plugin-react#consistent-components-exports

Remove the export const config and edits hot-refresh correctly, preserving count state.

System Info

- `@vitejs/plugin-react`: 6.0.1
- `vite`: 8.0.8
- `react`: 19.2.5

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @Artur-. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[ArnaudBarre]

Just tested your example against v5 and it correctly leads to hmr invalidate

This is expected, it has been working like this for a long time, I've built an eslint plugin to catch this.

If we didn't do that, changes to the config object will not be visible by importers, leading to broken updates.

Frameworks go around that by:

• react-router: forking the plugin and adding hmr handling for the frameworks export
• tanstack is hacking the export and then adds some code for making HMR works, but it doesn't work for everything