Running Remix on Cloudflare Workers about remix HOT 6 CLOSED

That's definitely a related but (I think) slightly different issue, @dbanisimov. Even without doing any of this work, we could still ship a service worker to handle all /_remix/data requests and inline the data loaders that are able to be run client-side into that worker.

As you say, this would help with latency on data requests. But in order to get full offline mode we would need to handle /_remix/manifest requests too, which we use to dynamically load more pieces of the site manifest as you navigate around.

from remix.

Another use case for that would be running loaders both on the server and in the service worker if the data access could be securely isomorphic. One particular idea that I've been pondering around is to use Firebase JS client-side SDK in the loaders. Once the initial server-rendered response is received and the service worker is installed all the subsequent data requests could be served client-side, reducing the latency and enabling other goodies, like offline persistence.

from remix.

This would be an incredible match, I would use the hell out of this.

FYI, there’s ES Module support coming soon, not sure if they will support importing other JavaScript files though. The fetch handler will be exported instead of being attached as an event listener, and it will receive an additional env argument:

export default {
  async fetch(request, env) {
    …
  }
}

from remix.

Without a server, how do we deal with SEO?
Wouldn't the Service-Worker run Remix be like a Progressive Web App?

from remix.

from remix.

I gave this a shot to get more family with the underling architecture of remix but I hit some roadblocks. Just documenting the issues here for someone else trying to get this working:

• The remix build currently lists no css files in build/assets.json so there is no easy way to cache them inside the service worker. (There is a workaround but I think that file should also list all resources too)
• Another issue stems from this pattern new Request(url.toString(), request); found in https://github.com/remix-run/remix/blob/main/packages/remix-server-runtime/server.ts#L632 and https://github.com/remix-run/remix/blob/main/packages/remix-server-runtime/server.ts#L638 when doing a reload while offline. The browser is creating a Request object with mode navigate and a service worker isn't allowed to use that as a RequestInit. The browser is throwing: TypeError: Failed to construct 'Request': Cannot construct a Request with a RequestInit whose mode member is set as 'navigate'. This is in accordance to Step 14. to 17. of the Spec

Having remix build around these platform features opens up so many possibility, very excited to look into this some more.

from remix.