In case you link or unlink a dependency, you'll need to force re-optimization on the next server start by using vite -force. Vite won't invalidate the dependencies when you use a feature like npm link. 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. 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. Optimized Dependencies Outdated pre-bundled deps when linking to a local package

The easiest way to achieve this is to run npx vite preview. You will need to access the file with http protocol. See Reason: CORS request not HTTP - HTTP | MDN for more information about why this happens.

If the HTML file output was opened with file protocol, the scripts won't run with the following error.Īccess 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.Ĭross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at file:///foo/bar.js. Build Built file does not work because of CORS error This can be caused by a circular dependency. If HMR is not handled by Vite or a plugin, a full reload will happen.Īlso if there is a dependency loop, a full reload will happen. If you are running Vite with WSL2, Vite cannot watch file changes in some conditions.

Related issue: #964 Vite does not detect a file change

Download phpstorm react native