Currently and actually most of the time I build front end layouts and styles which aren’t rendered in Wappler’s integrated browser view in the best/accurate way, especially when using partials or non Wappler scripts. Or when you cannot login as a user to view the page’s logged in state populated with data.
In the past, when working with VS Code, I used the Live Server extension, which on saving any changes on a page, whether layout or css, the page would refresh automagically in my browser window.
So my setup would be VS Code on one screen and Chrome/Safari/whatever on another.
A desirable setup for me would be Wappler on one screen and the browser on another where, if I save changes to the page, I do not have to tab through to the browser to have it in focus and click refresh or use short cut buttons to refresh the page. It is refreshed on server side by detecting changes in the code.
That is exactly what I mean. I use browser dev tools and many times different layouts and styling based on logged users. All of this makes viewing, analizing and troubleshooting in the browser so much easier by auto refreshing when any changes on a page or its styles are saved in Wappler.
We used https://browsersync.io/ for a bit, but it wasn't working great for us. It is the closest you can get to a working solution with Wappler, and not too difficult to set up with the documentation.