Route code hot swap
Business code such as src/routes/ uses a millisecond-level replacement path while the dev service process and connection state stay alive.
VEXTJS 0.3.24 / NATIVE API RUNTIME
VextJS
A Node.js framework built for high-performance RESTful APIs. Native fast path, three-tier server-side hot reload, CLI, validation, OpenAPI, and production runtime capabilities are ready in one project model.
T1Route code hot swap in 1-10 ms
T2Service/model structural reload in 5-50 ms
T3Config/plugin cold restart in 1-3 s
Nativehttp.createServer fast path
Hot Reload Pipeline
Three-tier server-side hot reload, so API development waits for fewer restarts.
Vext chooses a reload strategy by change boundary: replace what can be hot-swapped, rebuild only the affected structure when needed, 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.
5-50 msRuntime-boundary cold start
Configuration, plugin, and middleware changes perform a cold start so runtime boundaries are rebuilt correctly without sacrificing safety.
1-3 sPerformance 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.
API-oriented route core
File routes, three-part route definitions, and request context are organized around RESTful API services.
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
HonoLightweight modern ecosystem for edge scenarios and middleware composition.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 project.Verify hot reloadReview T1/T2/T3 trigger boundaries and dev server output.Prepare production deploymentReview build, start, graceful shutdown, and multi-process strategies.Reproduce performance benchmarksValidate throughput in different scenarios with repository benchmark scripts.