Void Cloud
questions
-
actions and loaders pattern for SSR apps
- I have a rough idea from having looked at how React Server components work.
-
this looks good for fullstack apps but not for apps with separate backend and front-end? What is my back? Hand has to serve multiple clients (mobile, web..)
it introduces a bunch of
- so it's like a t3-create-app? one of those popular starting templates that have all the currently most popular dependencies picked out for you?
Maybe not so much because it's a single dependency?
VOID: Vite native deployment Platform
From going to Vite app to deployed light app you still need to pick a framework, deployment platform, DB, aura, ORM, auth, queues, crons...
The idea is that it turns any vite app into a full-stack app with a single plugin.
wraps cloudflare cloud primitives?

(vite config file)
deploys to Cloudflare workers, that simple, no cloudflare knowledge or account required.
Every app get a .void.app domain

This are all cloudflare services (obviously)
(DB is simulated locally as well)
auth pkg is good, db schema is good.
- Drizzle here is very good, it's implemented in a way where it offers end to end type safety (type safety and same schema everywhere, front and backend)
- migrations are auto generated and applied on deploy

The void npm package has two parts,
- the SDK with all the features listed previously
- a meta framework with Pages + API routing with SSR, ISR, SSG, island, markdown..
work with all vite based meta frameworks (next, tanstack, sveltekit). Framework features wouldn't be needed since the meta frameworks handle that, so they would enjoy the SDK feature.

this is crazy, pretty much everything is streamlined and automated.
mcp that connects to deployment logs
code gen
db studio
you can devvelop lcally with remote dbs