aatd86 parent
For release but not for development.
Sufficient for the build step to take a long time and you start to notice the friction.
The web/browser should not rely on bundlers and compilation steps overall. This should remain optional.
Hot-reloads in a modern bundler like Vite will typically be instantaneous. Normally in development, only dependencies are bundles, and the files you write are served as-is (potentially with a per-file compilation step for e.g. jsx or TypeScript). That means that when you save a file, the bundler will run the compiler over that single file, then notify the hot-reload component in the browser to re-fetch it. That would be quick even if it were done in JavaScript, but increasingly bundlers use parts with in Go or Rust to ensure that builds happen every more quickly.
If you've got a huge project, even very quick bundlers will end up slowing down considerably (although hot reload should still be pretty quick because it still just affects individual files). But in general, bundlers are pretty damn quick these days, and getting even quicker. And of course, they're still fully optional, even for a framework like React.
Not really optional for react since it relies so heavily on jsx...
You can write react without it but then is it react? What about the libraries you may want to import or code that a llm will generate for you?
There should be better.
Hot reloading is pretty common now for React or other JavaScript projects