Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

Editing a component reloads the page instead of hot-updating it

ErrorEditing a component triggers a full page reload

Short answer

Fast Refresh only works for modules whose exports are React components. When a file also exports constants, hooks or helpers that change, or sits in an import cycle, Vite invalidates it and reloads more than you expect. Move non-components out, break the cycle, and check that the React plugin includes the file.

  • Applies to Vite 7, @vitejs/plugin-react 5, React 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Start Vite with HMR debugging and save the component. The log names the modules it walked and why the update went further than the file.

    npx vite --debug hmr
  2. 2Match what you see, then jump to its fix

    1. 1The file has a component plus an exported constant, hook, context or helper, and edits to it reset stateThe file exports something that is not a componentFix
    2. 2The HMR debug log shows a loop, or only some files fall back to a full reloadThe module sits in a circular importFix
    3. 3Files in one folder never refresh; they have an unusual extension or sit under a path you excludedThe plugin does not handle this fileFix

What does the error look like?

  • Editing a component triggers a full page reload
  • Component state resets on every save

Cause 1 of 3

The file exports something that is not a component

1Check

The React plugin states that for refresh to work correctly the file should only export React components. If an export changes in an incompatible way, the module is invalidated and the HMR update propagates up to importers. Plain constants are tolerated until their value changes.

grep -n "^export" src/components/Panel.tsx

2Fix

Move hooks, contexts, helpers and constants into their own files and keep component files for components. Add a lint rule that catches it.

// Panel.tsx exports only the component
export function Panel() { /* ... */ }
// panelContext.ts holds the context and the hook

3Verify

Edit the component and watch it update with state preserved.

npx vite --debug hmr

Confirmed by raw.githubusercontent.com

Did this fix it?

Cause 2 of 3

The module sits in a circular import

1Check

Vite's troubleshooting guide lists a full reload instead of HMR as caused by either no plugin handling the update or the update being in a circular dependency. The debug log prints the loop.

npx vite --debug hmr

2Fix

Break the loop: move the shared piece to a third module that both files import.

// before: a.tsx imports b.tsx, b.tsx imports a.tsx
// after: both import shared.ts

3Verify

Save one file of the former loop and confirm no reload happens.

npx vite --debug hmr

Confirmed by vite.dev

Did this fix it?

Cause 3 of 3

The plugin does not handle this file

1Check

The React plugin handles .js, .jsx, .ts and .tsx by default and skips node_modules. A custom include or exclude in vite.config can leave a folder out.

grep -n "react(" -A5 vite.config.*

2Fix

Widen include for the extension you use, or remove the exclude that matches your source folder. Keep node_modules excluded.

// vite.config.js
react({ include: /\.(mdx|js|jsx|ts|tsx)$/ })

3Verify

Edit a file from that folder and watch it refresh.

npm run dev

Confirmed by raw.githubusercontent.com

Did this fix it?

How do I stop it coming back?

  • One component per file, named export or default, with nothing else exported.
  • Use the ESLint react-refresh rule so a bad export is flagged while you type.
  • Keep import graphs one-directional: UI imports logic, never the reverse.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.