Route code hot swap
Business code such as src/routes/ uses a targeted replacement path while the dev service process and connection state stay alive.
AI-FIRST / FULL-STACK NODE.JS
VextJS
VextJS is an AI-first full-stack Node.js application framework for APIs and server-rendered React pages. Its conventions, scaffolding, typed contracts, OpenAPI, and machine-readable docs give AI coding assistants explicit inputs. AI-first does not mean a built-in LLM, Agent, RAG system, or inference runtime.
One routeJSON and SSR share URL ownership
ContractsRoute contracts feed validation, docs, and client types
Start smallFull-stack default, API-only supported
Nativehttp.createServer fast path
Hot Reload Pipeline
Three-tier backend hot reload plus frontend rebuild keeps development feedback tight.
Vext chooses a reload strategy by change boundary: replace what can be hot-swapped, rebuild frontend assets when client files change, and cold start only when runtime boundaries change.
Service and model structural reload
Changes in services, models, locale resources, and similar structures trigger local reloads instead of pushing every edit to a cold restart.
Reloads the affected graphRuntime-boundary cold start
Configuration, plugin, and middleware changes perform a cold start so runtime boundaries are rebuilt correctly without sacrificing safety.
Rebuilds runtime boundariesPerformance Stack
Performance is not a wrapper phrase; it is a set of engineering choices from the HTTP path to production guardrails.
The homepage keeps the framework's real engineering surface visible: Native fast path, route-core, schema/OpenAPI, CLI, and production delivery capabilities.
Native high-performance path
The Native Adapter stays close to Node.js HTTP and keeps routing lightweight with route-core.
Full-stack route core
File routes, three-part route definitions, generated client contracts, and request context are organized around one Vext project model.
Validation and OpenAPI
Declare parameter rules in route options so request validation and API documentation share one definition.
Ready-to-use CLI
Create, develop, build, and start commands are gathered under the framework entry, so new projects can begin immediately.
Runtime lifecycle
request, validation, response, service, fetch, and related hooks support plugins and cross-cutting logic.
Production safety capabilities
Rate limiting, structured errors, graceful shutdown, heartbeat monitoring, and multi-process deployment complete the delivery path.
Runtime Flexibility
Adapters are flexibility, not the homepage's main character.
Vext's main line is the framework's own API performance and developer experience. Adapters connect different HTTP ecosystems when needed, making migration and integration steadier.
NativeNative HTTP fast path for minimal dependencies and throughput-focused services.core
HonoWeb Standard APIs through Vext's Node.js bridge; only hono is required, and this is not an Edge runtime adapter.lean
FastifyMature high-performance ecosystem for complex plugin scenarios.plugin
ExpressCompatible with migration from traditional Node.js projects.classic
KoaFits onion-model flow and reuse of existing Koa code.flow
Production Ready
Secure, stable, shippable, and not stuck at the demo layer.
The Vext documentation entry should let teams quickly judge whether it can enter real server-side projects: rate limiting, graceful shutdown, rolling restart, cluster, i18n, structured errors, and OpenAPI all need to be visible.
Rate LimitBuilt-in rate limiting reduces abuse risk.
GracefulThe shutdown flow protects connections and requests.
ClusterMulti-process mode and heartbeats fit production supervision.
ErrorsBusiness codes, i18n, and JSON-safe details.
Next Steps
Jump directly into the engineering path you want to verify.
Create the first projectUse npx vextjs create to scaffold a TypeScript + React project.Verify reload behaviorReview backend T1/T2/T3 trigger boundaries and frontend rebuild output.Prepare production deploymentReview build, start, graceful shutdown, and multi-process strategies.Understand the benchmarksReview current measurements, comparison limits, adapter choices, and reproduction steps.