HMR about remix HOT 3 CLOSED

I've worked on a handful of "app-like apps" using Remix lately, and this is still near the top of my wish list.

Although ESBuild runs are fast, in my opinion, maintaining state between changes is a really underrated capability. It helps in cases like editing a popover state while it's open, editing a menu item while it's open, toggles, and so on. The failure case as described in the OP is a valid one for sure. But I don't know if guarding against that is worth sidestepping a potentially huge boost in DX.

from remix.

I appreciate the Remix team leaving the door open to this, and so just wanted to weigh in for team HMR a bit!

I understand Remix's goals with SSR first, and I also agree that with Edge computing, it's likely where everything is headed. However, I assume there are many others like me who are building apps with significant client-side state and interaction in order to create really rich UX. One example of such an app would be an online collaborative editor, something like Figma or Miro.

It would be awesome to have some fast refresh capabilities to make building that kind of apps on Remix an even nicer experience. On my current project, I even use the Vite HMR API to enhance the development experience according to our business requirements.

from remix.

My story is I want to use remix as the framework for a react-three-fiber app.

I really like remix, but compared to using vite and their react plugin I get real time updates both to css and 3d code which is a must have once you have tried it.

Could we tell remix which folders to do fast refresh on?

that way we could get fast refresh on ui components and in my case the react-three-fiber app, but still have full reloads when changing loaders or route adjacent modules.

from remix.