Removing a loader causes errors for users that have your app open already about remix HOT 2 CLOSED

This sounds more like a feature request than a bug. By removing a loader and deploying a new version of your remix server you have effectively removed an API endpoint that active clients rely on. Remix does not, by design, do any sort of active polling to the server to see if you've changed things - that would be something you need to wire up in your app.

A lot of folks do some form of polling via a fetcher to check a version from the server and force a hard reload in the uysers app (or prompt them) if they detect that a client is now stale.

You can also put a "Click here to reload" link that forces a hard reload in your error boundary to give users who might run into this error a way to load a fresh version of the app.

If you have an idea of how you'd like to see this done in a first class manner, please write up a Proposal in the Discussions tab for consideration!

from remix.

It would be nice if Remix included the current manifest version in every client-side fetch. This way, you could check on the server to see if the client matches the current server version and either proceed, return an error to refresh or redirect automatically.

from remix.