See Rollup's troubleshooting guide for more information too.
If the suggestions here don't work, please try posting questions on GitHub Discussions or in the
#help channel of Vite Land Discord.
Error: Cannot find module 'C:\foo\bar&baz\vite\bin\vite.js'
The path to your project folder may include
&, which doesn't work with
npm on Windows (npm/cmd-shim#45).
You will need to either:
- Switch to another package manager (e.g.
&from the path to your project
Requests are stalled forever
If you are using Linux, file descriptor limits and inotify limits may be causing the issue. As Vite does not bundle most of the files, browsers may request many files which require many file descriptors, going over the limit.
To solve this:
Increase file descriptor limit by
# Check current limit $ ulimit -Sn # Change limit (temporary) $ ulimit -Sn 10000 # You might need to change the hard limit too # Restart your browser
Increase the following inotify related limits by
# Check current limits $ sysctl fs.inotify # Change limits (temporary) $ sudo sysctl fs.inotify.max_queued_events=16384 $ sudo sysctl fs.inotify.max_user_instances=8192 $ sudo sysctl fs.inotify.max_user_watches=524288
If the above steps don't work, you can try adding
DefaultLimitNOFILE=65536 as an un-commented config to the following files:
For Ubuntu Linux, you may need to add the line
* - nofile 65536 to the file
/etc/security/limits.conf instead of updating systemd config files.
Note that these settings persist but a restart is required.
Network requests stop loading
When using a self-signed SSL certificate, Chrome ignores all caching directives and reloads the content. Vite relies on these caching directives.
To resolve the problem use a trusted SSL cert.
See: Cache problems, Chrome issue
You can install a trusted cert via the CLI with this command:
security add-trusted-cert -d -r trustRoot -k ~/Library/Keychains/login.keychain-db your-cert.cer
Or, by importing it into the Keychain Access app and updating the trust of your cert to "Always Trust."
431 Request Header Fields Too Large
When the server / WebSocket server receives a large HTTP header, the request will be dropped and the following warning will be shown.
Server responded with status code 431. See https://vitejs.dev/guide/troubleshooting.html#_431-request-header-fields-too-large.
This is because Node.js limits request header size to mitigate CVE-2018-12121.
To avoid this, try to reduce your request header size. For example, if the cookie is long, delete it. Or you can use
--max-http-header-size to change max header size.
Vite detects a file change but the HMR is not working
You may be importing a file with a different case. For example,
src/foo.js exists and
import './Foo.js' // should be './foo.js'
Related issue: #964
Vite does not detect a file change
If you are running Vite with WSL2, Vite cannot watch file changes in some conditions. See
A full reload happens instead of HMR
If HMR is not handled by Vite or a plugin, a full reload will happen.
Also if there is a dependency loop, a full reload will happen. To solve this, try removing the loop.
High number of HMR updates in console
This can be caused by a circular dependency. To solve this, try breaking the loop.
Built file does not work because of CORS error
If the HTML file output was opened with
file protocol, the scripts won't run with the following error.
Access to script at 'file:///foo/bar.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at file:///foo/bar.js. (Reason: CORS request not http).
See Reason: CORS request not HTTP - HTTP | MDN for more information about why this happens.
You will need to access the file with
http protocol. The easiest way to achieve this is to run
npx vite preview.
Outdated pre-bundled deps when linking to a local package
The hash key used to invalidate optimized dependencies depend on the package lock contents, the patches applied to dependencies, and the options in the Vite config file that affects the bundling of node modules. This means that Vite will detect when a dependency is overridden using a feature as npm overrides, and re-bundle your dependencies on the next server start. Vite won't invalidate the dependencies when you use a feature like npm link. In case you link or unlink a dependency, you'll need to force re-optimization on the next server start by using
vite --force. We recommend using overrides instead, which are supported now by every package manager (see also pnpm overrides and yarn resolutions).
Module externalized for browser compatibility
When you use a Node.js module in the browser, Vite will output the following warning.
Module "fs" has been externalized for browser compatibility. Cannot access "fs.readFile" in client code.
This is because Vite does not automatically polyfill Node.js modules.
We recommend avoiding Node.js modules for browser code to reduce the bundle size, although you can add polyfills manually. If the module is imported from a third-party library (that's meant to be used in the browser), it's advised to report the issue to the respective library.
Syntax Error / Type Error happens
Vite cannot handle and does not support code that only runs on non-strict mode (sloppy mode). This is because Vite uses ESM and it is always strict mode inside ESM.
For example, you might see these errors.
[ERROR] With statements cannot be used with the "esm" output format due to strict mode
TypeError: Cannot create property 'foo' on boolean 'false'
If these code are used inside dependencies, you could use
yarn patch or
pnpm patch) for an escape hatch.
Some browser extensions (like ad-blockers) may prevent the Vite client from sending requests to the Vite dev server. You may see a white screen without logged errors in this case. Try disabling extensions if you have this issue.
Cross drive links on Windows
If there's a cross drive links in your project on Windows, Vite may not work.
An example of cross drive links are:
- a virtual drive linked to a folder by
- a symlink/junction to a different drive by
mklinkcommand (e.g. Yarn global cache)
Related issue: #10802