Error AtlasError Documentation and Resolution
Back to searchMore Vite errors

Vite

Vite performs a full reload instead of Hot Module Replacement

A full reload happens instead of HMR.

Vite fell back to a full page reload because the changed module is not handled safely by HMR or there is a dependency loop preventing a targeted update.

A full reload happens instead of HMRdevelopment servers

Observed message

A full reload happens instead of HMR.

Why it happens

  • The changed module is not handled by Vite or a plugin for HMR.
  • A dependency loop is preventing safe hot updates.
  • The module graph changed in a way that requires a full reload.

How to fix it

  1. Inspect whether the affected module actually supports HMR in your stack.
  2. Check for circular dependencies that can force a full reload.
  3. Adjust plugin or module structure so the changed file can participate in hot updates safely.

Official reference

Vite: Troubleshooting

Related errors

Error: Cannot find module 'C:\foo\bar&baz\vite\bin\vite.js'Vite cannot start because the project path contains an ampersand on WindowsCross drive links on WindowsVite cross-drive links do not work on WindowsPort 5173 is already in useVite dev server port already in useRequests are stalled foreverVite dev server requests are stalled forever

Explore more

ViteBrowse more Vite errorsdevelopment serversBrowse more development servers errors
Vite full reload happens instead of HMR: causes and fixes | Error Atlas