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

TODO: vite-node-miniflare #127

Closed
13 of 19 tasks
hi-ogawa opened this issue Dec 14, 2023 · 4 comments
Closed
13 of 19 tasks

TODO: vite-node-miniflare #127

hi-ogawa opened this issue Dec 14, 2023 · 4 comments

Comments

@hi-ogawa
Copy link
Owner

hi-ogawa commented Dec 14, 2023

Remaining issues from


@alexturpin
Copy link

Hey, just found your repo and wanted to say that I think you're doing really awesome work. It's been a long struggle to find something with great DX to develop full stack React apps on Cloudflare with Vite, and it looks like you're working on literally every problem with that right now.

Maybe this isn't something you're interested in, but to me it looks like you've got all the ingredients for a mini framework to do React on Cloudflare workers, something that now abandoned https://github.com/flareact/flareact was aspiring to. I'll be playing with your fuller react-router / HatTip example with that in mind.

Either way, please keep up the great work and I'll be watching closely! Would love to contribute as well if you get to a point where that makes sense to you.

@hi-ogawa
Copy link
Owner Author

@alexturpin Thanks for the interest! This package vite-node-miniflare was mostly an early experiment and I'm not actively developing it other than giving some feedback to Vite team.

The good new is that, in Vite 6, they are planning to include a new feature to allow non-NodeJs runtime integration easier and indeed collaborating with Cloudflare team on this aspect, so you might want to follow the development there. Please check out a following discussion and if you have any feedback, please feel free to comment!

Let me close this issue for now as it's a bit obsolete and it served its purpose.

@alexturpin
Copy link

@hi-ogawa totally understand, thanks for taking the time to respond! I think I've actually found a pretty ideal solution in HonoX which leverages the new workerd getPlatformProxy.

@hi-ogawa
Copy link
Owner Author

Right, getPlatformProxy is the current solution by Cloudflare team, but they are now exploring to bring genuine workerd runtime for the entire server side code during development (not only cf resource bindings).
You can find some early proof of concepts here if you are interested

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

2 participants