VextJS
  • English

      • 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.

      Quick startThree-tier reloadBenchmarkSupport & servicesGitHub
      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.

      T1 / code

      Changes to existing backend files

      An existing file in a soft scope such as src/routes/ usually compiles and reloads affected modules; failures may escalate to a cold restart.

      Normally keeps the application worker alive
      T2 / struct

      Added, removed, or fully reloaded files

      Adding or removing routes, services, middleware, Models, or locale resources in a soft scope rescans compile entries and updates runtime state.

      Reloads the affected graph
      T3 / cold

      Runtime-boundary cold start

      Changes to configuration, plugins, preload entries, or startup dependencies cold restart the application worker; middleware normally remains in the soft scope.

      Rebuilds runtime boundaries

      Performance Stack

      Framework capabilities from HTTP handling through build and deployment.

      Start with routing, validation, and typed contracts. Enable frontend, documentation, and runtime features as the application needs them; consult the corresponding guides for their prerequisites and limits.

      fast path

      Native high-performance path

      The Native Adapter stays close to Node.js HTTP and keeps routing lightweight with route-core.

      router

      Full-stack route core

      File routes, three-part route definitions, generated client contracts, and request context are organized around one Vext project model.

      schema

      Validation and OpenAPI

      Declare parameter rules in route options so request validation and API documentation share one definition.

      cli

      Ready-to-use CLI

      Create, develop, build, and start commands are gathered under the framework entry, so new projects can begin immediately.

      hooks

      Runtime lifecycle

      request, validation, response, service, fetch, and related hooks support plugins and cross-cutting logic.

      safe ship

      Production safety capabilities

      Enable rate limiting, structured errors, graceful shutdown, and multi-process monitoring when needed, then verify them in the target environment.

      Runtime Flexibility

      Choose an HTTP adapter for your integration needs.

      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; check Vext adapter boundaries before integrating native plugins.plugin
      ExpressWhen migrating Express projects, adapt to the Vext request and middleware contracts.classic
      KoaSupports onion-model flow; verify how existing Koa middleware integrates.flow

      Production Operations

      Verify runtime and deployment capabilities in the target environment.

      Before deployment, check feature switches, platform support, and timeout budgets. Verify rate-limit failures, shutdown, and worker replacement. Configuration support does not mean the application has passed production acceptance.

      Rate LimitDisabled by default; after enabling it, verify quotas and storage failures.
      GracefulWaits for requests and resource cleanup within the shutdown budget.
      ClusterMulti-process mode and heartbeats support 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 the versioned historical sample, adapter comparison, and method for measuring a new baseline.