I'm running Windows 11 and in command prompt I execute "npx supabase functions serve" to run my functions. Every time I save a file in VS Code thereafter it registers the "change" twice and proceeds to reload the functions, stop all services again immediately afterwards, then reloads a second time. This occurs on every file save, even if no changes were made.
Is there a way to fix the hot reload mechanism that runs to observe file changes when serving supabase functions locally? It adds an extra second to every reload and I know this will drive me nuts in the long run. I've spent a lot of time trying to figure out the root cause and fix it but for the life in me I cannot.
What's causing this and how can I fix it?
The user experiences double reloading of Supabase functions on Windows 11 when saving files in VS Code. This issue occurs even when no changes are made, causing unnecessary delays. The user seeks a solution to optimize the hot reload mechanism when serving functions locally.
I stopped reading at Windows 11! Jokes aside, check there are no other code change triggers in VS Code.