You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like a couple of other people in discord and on this repo, I've hit a few snags with the Cloudflare template, just to realize that the vite miniflare plugin was just an experiment and doesn't seem like it's very future proof.
While it has its issues, the cloudflare dev proxy from Remix was pretty solid (as long as you understood the difference between developing in Node vs developing in Wrangler/Workerd/Miniflare and the gotchas you might hit). Wrangler's local development experience isn't particularly robust, so I've usually just had my regular dev script that uses Vite, and another script to test in Wrangler when I have a Cloudflare specific issue to debug.
There's also a PR from someone else, #44 to go back to the dev proxy.
But I'm curious if there was a discussion around why the template was moved away from it and toward the miniflare plugin with RR7, considering it's pretty much deprecated.
I'd definitely suggest keeping the Remix Cloudflare dev proxy as the default in Cloudflare templates until something significantly more robust becomes available, even if it has its limitations. At least it works as advertised~
The text was updated successfully, but these errors were encountered:
As per this comment from the author
Like a couple of other people in discord and on this repo, I've hit a few snags with the Cloudflare template, just to realize that the vite miniflare plugin was just an experiment and doesn't seem like it's very future proof.
While it has its issues, the cloudflare dev proxy from Remix was pretty solid (as long as you understood the difference between developing in Node vs developing in Wrangler/Workerd/Miniflare and the gotchas you might hit). Wrangler's local development experience isn't particularly robust, so I've usually just had my regular dev script that uses Vite, and another script to test in Wrangler when I have a Cloudflare specific issue to debug.
There's also a PR from someone else, #44 to go back to the dev proxy.
But I'm curious if there was a discussion around why the template was moved away from it and toward the miniflare plugin with RR7, considering it's pretty much deprecated.
I'd definitely suggest keeping the Remix Cloudflare dev proxy as the default in Cloudflare templates until something significantly more robust becomes available, even if it has its limitations. At least it works as advertised~
The text was updated successfully, but these errors were encountered: