Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@hiogawa/vite-node-miniflare is no longer maintained #52

Open
Phoenixmatrix opened this issue Jan 2, 2025 · 0 comments
Open

@hiogawa/vite-node-miniflare is no longer maintained #52

Phoenixmatrix opened this issue Jan 2, 2025 · 0 comments

Comments

@Phoenixmatrix
Copy link

Phoenixmatrix commented Jan 2, 2025

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~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant