The filesystem is the architecture.
React pages and NestJS controllers stay in one application without collapsing into one bundle.
Explore the primitive →Ness.js 7Full-stack React framework
Build React apps that own the whole request.
Route the interface, server data and public APIs from one filesystem. Ness keeps the Web platform visible and the production runtime included.
$
npm install -g @nessframework/cliNode 16+route manifestready
/page.jsxSSR/docs/:slug[slug]/page.tsxdynamic/api/healthhealth.controller.tsNestJS/*not-found.tsx404One application, end to end
The framework stays out of the platform’s way.
Request and Response all the way down.
Loaders and actions use standard Web APIs, with typed route data and progressive enhancement built in.
Explore the primitive →Stream first. Cache with intent.
SSR, prerendering, ISR and tagged invalidation share one predictable production runtime.
Explore the primitive →One CLI for the workflow
From empty directory to production route tree.
Create the app, add official plugins, generate route and server modules, update packages, verify configuration and serve the same build you deploy.
Explore the Ness CLIness — zsh●
$ ness new studio --template typescript
✓ Installed @nessframework/core and @nessframework/cli
$ ness g controller users
✓ app/server/users/users.controller.ts
$ ness add tailwind --devNess.js v7
Create an application