cloudflare/vinext

Purpose and principal workflow

vinext reimplements much of the Next.js API surface on Vite, with Cloudflare Workers as its primary deployment target. The main workflow begins when an application developer runs Vite or the vinext CLI against a Next.js-style project: vinext configures the build and runtime, discovers and serves App Router or Pages Router routes, and returns rendered responses in development or production. Cloudflare deployment is an additional path. The repository also contains the vinext.dev website and its compatibility-results data flow.

Components

Framework setup and build

• Vite plugin entry — packages/vinext/src/index.ts: exposes vinext’s Vite integration, which the README documents as the way to run a project using vinext().

• CLI and project initialization — packages/vinext/src/cli.ts: provides the documented vinext command-line entry; migration and configuration generation are implemented separately.

• Next.js configuration handling — packages/vinext/src/config/next-config.ts: substantial configuration module listed among the core files; the README says vinext loads existing next.config.js configuration.

• Project migration — packages/vinext/src/init.ts: implements vinext init, the documented migration workflow.

• New-project scaffolding — packages/create-vinext-app/src/index.ts: implements the create-vinext-app setup flow; its source references vinext initialization and platform setup.

• Next.js type compatibility — packages/types/next/index.d.ts: repository path for the compatibility type package; the README documents support for commonly used next/* modules, though this file’s precise role is not shown in the excerpts.

Routing and request execution

• Route matching and validation — packages/vinext/src/routing/route-validation.ts: part of the routing subsystem; the Pages request pipeline references route validation and routing utilities.

• Shared request security and normalization — packages/vinext/src/server/request-pipeline.ts: handles shared request checks, including base-path handling, middleware headers, and open-redirect protection.

• Pages Router request pipeline — packages/vinext/src/server/pages-request-pipeline.ts: owns the documented-in-code nine-step Pages Router request order; callers inject callbacks.

• App Router page execution — packages/vinext/src/server/app-page-execution.ts: implements a substantial App Router execution stage; its exact call chain is not established by the supplied excerpts.

• Next.js server API shims — packages/vinext/src/shims/server.ts: provides NextRequest, NextResponse, and related APIs using standard Web request/response types.

• Request/render context state — packages/vinext/src/shims/internal/work-unit-async-storage.ts: tracks request, prerender, and cache work-unit contexts with async-local storage.

• Browser App Router navigation — packages/vinext/src/server/app-browser-navigation-controller.ts: coordinates pending navigation commits and visible state updates; imports the browser-state and visible-commit helpers.

Cloudflare runtime and response caching

• Cloudflare deployment CLI — packages/cloudflare/src/cli.ts: repository entry for the Cloudflare command package; the README documents @vinext/cloudflare deploy.

• Cloudflare CDN cache adapter — packages/cloudflare/src/cache/cdn-adapter.worker.ts: Worker-side CDN response caching, including cache identity construction and shared-cache policy checks.

• Cloudflare response-store adapter — packages/cloudflare/src/cache/response-store-adapter.worker.ts: adapts response-store operations for Workers and handles replayable invocations and paired App Router document/RSC parts.

• Workers response-store binding — packages/workers-response-store/src/binding.ts: exposes the response-store binding implementation; the Cloudflare adapter imports its public types.

• Durable Object metadata and storage coordination — packages/workers-response-store/src/metadata-do.ts: maintains response metadata in Durable Object SQL and coordinates R2 updates and cleanup.

Website and compatibility data

• Website routes and landing page — apps/web/app/page.tsx: implements the homepage; the repository is documented as vinext’s website.

• Compatibility dashboard — apps/web/app/compatibility/page.tsx: substantial dashboard route; supporting suite and router classification logic is implemented in apps/web/app/compatibility/suite-support.ts and apps/web/app/compatibility/router-buckets.ts.

• Compatibility ingestion endpoints — apps/web/app/api/compatibility/route.ts: authenticates and upserts compatibility run counts and file results; apps/web/app/api/compatibility/classify/route.ts separately upserts router classification metadata.

• Compatibility database schema and client — apps/web/app/lib/db/schema.ts: defines compatibility data tables; apps/web/app/lib/db/client.ts creates a database client using that schema.

• Blog content and feed — apps/web/app/blog/_source.ts: supplies blog source data; apps/web/app/blog/feed.xml/route.ts uses it to produce the feed.

External actors

• Application developer — (null repository path): runs Vite or a vinext CLI command in a consuming project.

• Consuming Next.js-style application — (null repository path): supplies the project routes, configuration, and application code vinext builds and serves.

• Browser or HTTP client — (null repository path): requests application pages and APIs and receives responses.

• Cloudflare Workers platform — (null repository path): runs deployed Workers and provides the platform bindings used by the response store.

• Compatibility-suite CI caller — (null repository path): submits compatibility run results and classifications to the website’s ingestion endpoints.

Relationships

• Application developer -> Vite plugin entry: invokes Vite with vinext; evidence: README.md.

• Application developer -> CLI and project initialization: runs documented migration or CLI commands; evidence: README.md.

• Vite plugin entry -> Next.js configuration handling: plugin loads the project’s Next configuration, as documented; evidence: README.md.

• Vite plugin entry -> Route matching and validation: plugin provides the framework route integration; evidence: none (inferred from documented Vite integration and routing subsystem).

• Browser or HTTP client -> Shared request security and normalization: sends a request that is checked and normalized; evidence: packages/vinext/src/server/request-pipeline.ts.

• Pages Router request pipeline -> Shared request security and normalization: imports and uses the shared request pipeline; evidence: packages/vinext/src/server/pages-request-pipeline.ts.

• Pages Router request pipeline -> Route matching and validation: imports route-validation and routing utilities; evidence: packages/vinext/src/server/pages-request-pipeline.ts.

• Route matching and validation -> Consuming Next.js-style application: routes requests to application-defined pages; evidence: none (inferred; exact runtime dispatch is not shown).

• Browser App Router navigation -> Browser or HTTP client: updates browser-visible navigation state; evidence: packages/vinext/src/server/app-browser-navigation-controller.ts.

• Cloudflare deployment CLI -> Cloudflare Workers platform: deploys the application to Workers; evidence: README.md.

• Cloudflare CDN cache adapter -> Workers response-store binding: no direct call is established in the supplied excerpts; evidence: none (inferred only as part of the documented Cloudflare cache integration).

• Cloudflare response-store adapter -> Workers response-store binding: imports response-store types; evidence: packages/cloudflare/src/cache/response-store-adapter.worker.ts.

• Workers response-store binding -> Durable Object metadata and storage coordination: binding references the metadata Durable Object; evidence: packages/workers-response-store/src/binding.ts.

• Compatibility-suite CI caller -> Compatibility ingestion endpoints: submits run counts and file results; evidence: apps/web/app/api/compatibility/route.ts.

• Compatibility-suite CI caller -> Compatibility ingestion endpoints: submits classification metadata; evidence: apps/web/app/api/compatibility/classify/route.ts.

• Compatibility ingestion endpoints -> Compatibility database schema and client: run ingestion writes run/file rows, and classification ingestion uses the database client to write classifications; evidence: apps/web/app/api/compatibility/route.ts and apps/web/app/api/compatibility/classify/route.ts.

• Compatibility database schema and client -> Compatibility dashboard: the dashboard presents compatibility results; evidence: none (inferred; dashboard query wiring is not sampled).

Coverage limits

The README and tree establish broad supported features, but the excerpts do not show the full Vite plugin registration, production server dispatch, App Router rendering chain, Cloudflare deploy sequence, or dashboard reads. Those relationships are left out or marked inferred rather than asserted as concrete calls.