Error AtlasError Documentation and Resolution
Back to searchMore Vite errors

Vite

Vite app shows a white screen because browser extensions are blocking requests

You may see a white screen without logged errors.

A browser extension such as an ad blocker can prevent the Vite client from sending or receiving requests, leaving the page blank without obvious application errors.

White screen without logged errorsruntime

Observed message

You may see a white screen without logged errors.

Why it happens

  • A browser extension is blocking requests to the Vite dev server or client runtime.
  • Privacy tooling or ad blockers are interfering with dev-server traffic.
  • The blank page is caused by browser-side request blocking rather than app code.

How to fix it

  1. Test the app with browser extensions disabled.
  2. Whitelist the local dev origin if an extension is blocking requests.
  3. Use the network panel to confirm whether dev-server requests are being cancelled or blocked.

Official reference

Vite: Troubleshooting

Related errors

TypeError: Failed to fetch dynamically imported moduleVite app failed to fetch a dynamically imported moduleAccess to script at 'file:///...' from origin 'null' has been blocked by CORS policyVite built file failed because it was opened over the file protocolTypeError: Cannot create property 'foo' on boolean 'false'Vite surfaced a strict-mode type error from incompatible codeError: Cannot find module 'C:\foo\bar&baz\vite\bin\vite.js'Vite cannot start because the project path contains an ampersand on Windows

Explore more

ViteBrowse more Vite errorsruntimeBrowse more runtime errors
Vite white screen without logged errors: causes and fixes | Error Atlas