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
When Vite's development server is running under Deno and a file it is tracking is modified by Neovim, a change is registered in every file that Vite is tracking and all are reloaded.
Because of this HMR is unusable. Vite will inevitably detect too many changes and overwhelm the refresh system leading to either a crash and relaunch or at best a total source reload.
This only happens under Deno after version 2.1.2, earlier versions do not exhibit this issue.
Some editors other than Neovim also do not trigger this issue (for instance a filesave in VSCode does not cause this to happen). There seems to be something specific about the way Neovim saves a file that confuses Vite's file watcher when run under Deno 2.1.2 and later.
I have tested many versions of Neovim (v9.x, v10.x, nightly) with and without plugins enabled, and all trigger this issue. Many versions of Vite (v4.x, v5.x, v6.x) as well, and all trigger this issue.
The problem has specifically been observed in Neovim (any version), Vite (any version), and Deno (2.1.2, 2.1.3, and 2.1.4)
Version: Deno 2.1.2, 2.1.3, 2.1.4
OS: Arch Linux
When Vite's development server is running under Deno and a file it is tracking is modified by Neovim, a change is registered in every file that Vite is tracking and all are reloaded.
Because of this HMR is unusable. Vite will inevitably detect too many changes and overwhelm the refresh system leading to either a crash and relaunch or at best a total source reload.
This only happens under Deno after version 2.1.2, earlier versions do not exhibit this issue.
Some editors other than Neovim also do not trigger this issue (for instance a filesave in VSCode does not cause this to happen). There seems to be something specific about the way Neovim saves a file that confuses Vite's file watcher when run under Deno 2.1.2 and later.
I have tested many versions of Neovim (v9.x, v10.x, nightly) with and without plugins enabled, and all trigger this issue. Many versions of Vite (v4.x, v5.x, v6.x) as well, and all trigger this issue.
The problem has specifically been observed in Neovim (any version), Vite (any version), and Deno (
2.1.2
,2.1.3
, and2.1.4
)Here is a simple reproduction of the issue https://github.com/GunnerGuyven/deno-issue-example-1
Downgrading Deno using
sudo deno upgrade 2.1.1
also avoids this issue.The text was updated successfully, but these errors were encountered: