You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server seemingly has issues identifying which files have already been loaded after a hot reload resulting in duplicate files causing errors and other unexpected runtime behavior. Here's my source list after the reload in Chrome's inspect panel:
The issue goes away if all files are imported their absolute paths (e.g. '/main.js' rather than './main.js') as described here. It appears that Vite isn't using a canonical path to identify the unique set of files for the update.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Describe the bug
When running the dev server on a project where:
The server seemingly has issues identifying which files have already been loaded after a hot reload resulting in duplicate files causing errors and other unexpected runtime behavior. Here's my source list after the reload in Chrome's inspect panel:
The issue goes away if all files are imported their absolute paths (e.g. '/main.js' rather than './main.js') as described here. It appears that Vite isn't using a canonical path to identify the unique set of files for the update.
Reproduction
vite-test.zip
Steps to reproduce
unpack the zip files
change a file, save and check the source file list in browser's inspect panel.
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: