Error AtlasError Documentation and Resolution
Back to searchMore Vite errors

Vite

Vite cross-drive links do not work on Windows

Cross drive links on Windows

Vite development setups can break on Windows when linked dependencies span different drives, because path resolution and watcher behavior become inconsistent.

Cross drive links on Windowsdevelopment servers

Observed message

Cross drive links on Windows

Why it happens

  • The app and the linked dependency are stored on different Windows drives.
  • The development setup relies on filesystem links across drive boundaries.
  • Vite watcher and path-resolution behavior is inconsistent in that layout.

How to fix it

  1. Move linked workspaces onto the same drive if possible.
  2. Avoid cross-drive symlink setups for local Vite development on Windows.
  3. Retest after restructuring the workspace so app code and linked packages resolve on the same volume.

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 WindowsPort 5173 is already in useVite dev server port already in useRequests are stalled foreverVite dev server requests are stalled forever431 Request Header Fields Too LargeVite dev server returns 431 Request Header Fields Too Large

Explore more

ViteBrowse more Vite errorsdevelopment serversBrowse more development servers errors
Vite cross drive links on Windows: causes and fixes | Error Atlas