TODO: vite-node-miniflare

[hi-ogawa]

Remaining issues from

• feat: create vite-node-miniflare package (run vite-node/client on workerd) #123

---

• cjs dep pre-bundling (feat(vite-node-miniflare): add vitePluginPreBundle #128)
  • Interesting. It seems nodejs is actually using this https://github.com/nodejs/cjs-module-lexer (found via evanw/esbuild#442 (comment))
  • esm.sh ended up with own solution https://github.com/esm-dev/esm.sh/tree/main/packages/esm-cjs-lexer
  • but this requires handling re-exports between cjs as an extra steps... direct execution is fine then?
  • cache feat(vite-node-miniflare): cache pre-bundle #139
• debug mode for vite-node (feat(vite-node-miniflare): support vite-node/client debug #129)
  • need to somehow inject DEBUG=vite-node:client:execute etc...
• error stack trace feat(vite-node-miniflare): support error stack sourcemap #144
• integrate wrangler dev (use unstable_dev api instead of Miniflare?)
• demo
  • vite-grob-routes feat(vite-node-miniflare): add React Router SSR demo #132
    • virtual module
    • react-router
  • remix feat(vite-node-miniflare): add Remix demo #134
    • custom RPC for DevServerHooks
    • custom virtual module invalidation
  • integrate miniflare service (e.g. kv)
• rename package vite-node-workerd?
• organize demo into separate workspaces
  • otherwise @hiogawa/vite-node-miniflare's devDependencies are becoming too messy
  • refactor(vite-node-miniflare): move examples to separate workspaces #138
• use h3 instead of hattip for internal? refactor(vite-node-miniflare): replace hattip with h3 for internal middleware #135
• replace vite-node with vite runtime feat: integrate vite runtime #155
• handle HMRPayload in real time (websocket, birpc, sse?)
  • https://github.com/sapphi-red/vite-envs/tree/use-vite-runtime
• redirect response is stuck in miniflare.dispatchFetch?
  • 🐛 BUG: does Miniflare.dispatchFetch handle redirect Response from worker script? cloudflare/workers-sdk#5018

[alexturpin]

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]

@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!

• Environment API vitejs/vite#16358
• feat: v6 - Environment API vitejs/vite#16471

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

[alexturpin]

@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]

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

• https://github.com/dario-piotrowicz/vite-environment-6.0.0-alpha-experimentations
• https://github.com/jacob-ebey/cf-vite-plugin
• https://github.com/hi-ogawa/vite-environment-examples