Blog
Release notes and design write-ups from the Devora.js project — what changed, why, and what to do about it.
RSS feed · Written by hassanalsa3aka
Devora.js 0.3.5: less work per request, and what it did and did not change
Five profiled changes to devora start, one clearer message for a missing session store, and the measured effect: where Devora.js is ahead, level, and still behind.
Devora.js 0.3.4: catch-all routes and a faster static path
Catch-all routes for pages and API routes, pre-rendered pages served from memory with ETags, correct content types, sitemap URLs from getStaticParams(), and the version number that skipped 0.3.3.
Your first multi-app project in 15 minutes
Scaffold a Devora.js project, run it, build and serve the build, then add a second app that shares one function and one login with the first. Every command was run.
Devora.js 0.3.2: what changed and what to do
Request access in loaders, actions that return data, error pages, a head API, cookie and proxy settings, CORS, and a fixed Vercel runtime — plus the changes an existing app has to act on.
Why multi-app is a first-class idea
Most products are more than one app. What Devora.js does about that, what it costs, and where a monorepo tool or one big app is still the better fit.
One repo, several Vercel projects: deploying a multi-app project
Each app in a Devora.js project is its own Vercel project. The settings, the session store, the api/ folder trap, and the repo-root alternative.