[browser-esbuild] live-reload=false workflow is less convenient now

[undsoft]

Command

serve

Description

I often work with live-reload disabled. This is helpful when working on CSS changes, I can try things in browser and then make multiple edits in files before manually reloading.
It's also faster when working on a laptop.

Before esbuild:

1. Make changes.
2. Refresh page.
3. Page reloads after new changes have been compiled.

With esbuild:

1. Changes.
2. Refresh.
3. Page reloads immediately before changes have been compiled. Now I need to monitor terminal and reload the page after successful compilation.

Describe the solution you'd like

I was okay with the old behaviour where server wouldn't respond before successful compilation.

A less desired alternative would be to log Vite messages in browser's console, so that I can tell when compilation has finished there.

Describe alternatives you've considered

No response

[sruszczynski]

One of the most frustrating things for me after switching to esbuild. So far, reloading the tab in the browser has been held up until the project rebuild is complete. Currently the old version is being served...

[Licen-it]

I have a similar issue, I'm running the server not using ng serve, and directly having my serve to load from the output folder, and i was relying on the build-watch completion to refresh the page, but now since i switched to esbuild, once the build completes, the new files are not physically written on the file system and refreshing the browser won't load the new changes (i have to wait a few seconds after the build completes before refreshing the browser)