[Bug] Weird behavior of Remix in dev mode

[lagz0ne]

What version of Remix are you using?

1.1.3

Steps to Reproduce

Environment
Windows 11
WSL2

Reproducible code https://github.com/lagz0ne/remix-bug

The code doesn't really work in Dev mode but works well in Production mode
The action part seems to be called but didn't persist the change to the content. As such, the loader takes the content from the original stage, not sure this has anything to do with the model of rebuilding (please have a look at the index route in the repository).

Expected Behavior

Works in Dev mode

Actual Behavior

Doesn't function in dev mode

[cmd-johnson]

See #1818 and #1832.
In dev mode, Remix currently purges the require cache on every single request, meaning your cache object will be initialized to ["1"] every time you navigate to your Index route.

You can work around this by attaching your cache to the global object. This is how I did it:

const cache = (() => {
  const globalCache = global as { cache?: string[] };
  if (!globalCache.cache) {
    globalCache.cache = ["1"];
  }
  return globalCache.cache;
})();

(If you do this in different parts of the app, you might want to use a more specific name than just cache to add to the global object to prevent name clashes)

This might be a bit verbose, but it's probably the best you can do for now. Just remember that when using the global object, the cache will only be re-created when you restart your dev server. So every time you change your cache initialization code, you'll have to manually restart your app.

[lagz0ne]

Thank @cmd-johnson, that's an awesome explanation and work around

[machour]

This is already described in https://remix.run/docs/en/v1/other-api/serve, but could benefit from an additional example and workaround as provided by @cmd-johnson

[balzdur]

It may be similar to this issue.

A promising solution is proposed here.

In the meantime, you can use patch-package as proposed here.

UPDATE: for v1.10.1 you can use the new patch provided here

[pcattori]

Fixed by #5133 which will make the new dev server available in the next minor release under the unstable_dev future flag.