3 ms·
> Separate development pages to test out small parts > of an application is how you avoid replicating state. > But today's web development environment i
by always_good 10y ago
> Separate development pages to test out small parts
> of an application is how you avoid replicating state.
> But today's web development environment is so wrapped
> up in tooling and build complexity that creating a new
> page to test out a small part of the application is
> actually really hard to do.
I don't think you understand what "hot code reloading" means, because isolating a widget on a separate page isn't a solution to what hot code reloading solves.
It's not just a browser auto-refresh when you save a file. It's the browser refreshing with the same state that was on the page.
Even if you isolate a somewhat complicated <form> on its own /form-test-page, you still don't want to drill down into the form state you're testing as you make changes to the UI.
For example, it would remember that you had the datepicker open with Jan 2017 - Oct 2018 selected as you fix a bug regarding the cross-year boundary. Stuff like that, useful any time you have some Javascript on the page.