Uh oh!
There was an error while loading. Please reload this page.
[ci] Enable NestJS e2e-vercel-prod and add to docs as "experimental" - #3011
Conversation
Enables the Vercel production e2e suite against the NestJS workbench, using the `workbench-nestjs-workflow` Vercel project (root `workbench/nest`). No test-code changes are required: `packages/core/e2e/utils.ts` already carves out `nest` for step/workflow source maps, and `e2e.test.ts`/`e2e-agent.test.ts` handle non-Next/non-agent apps through the generic World + `.well-known/workflow` path. The nest workbench already exposes `POST /api/test-direct-step-call`, the full example workflow set, and the flow/webhook/manifest endpoints via `workflow-nest build --vercel`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Wielander <peter.wielander@vercel.com>
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (55 failed)astro (5 failed):
example (5 failed):
express (5 failed):
fastify (5 failed):
hono (5 failed):
nextjs-turbopack (5 failed):
nextjs-webpack (5 failed):
nitro (5 failed):
nuxt (5 failed):
sveltekit (5 failed):
vite (5 failed):
📋 Other (10 failed)e2e-vercel-prod-nest (5 failed):
e2e-vercel-prod-tanstack-start (5 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 📋 Other
✅ vercel-multi-region
❌ Some E2E test jobs failed:
Check the workflow run for details. |
📊 Workflow Benchmarkscommit Backend:
📜 Previous results (2)289071bMon, 20 Jul 2026 21:18:47 GMT · run logs
9615b13Mon, 20 Jul 2026 20:29:54 GMT · run logs
Best/P75/P90/P99 deltas compare against the most recent benchmark run on Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) 🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120 All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor ( Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the |
On Vercel the nest project's `vercel-build` script is run directly, so unlike the framework workbenches (whose `vercel build` goes through Turbo and builds `packages/*` first), the workspace SDK dist was never built — the build failed with `Cannot find module '.../packages/nest/dist/cli.js'`. Prepend `pnpm -w run build` so the SDK packages are compiled (Turbo-cached) before the NestJS app and the `workflow-nest build --vercel` step run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Wielander <peter.wielander@vercel.com>
| <Nest className="size-16 dark:invert" /> | ||
| <span className="font-medium">NestJS</span> | ||
| <Badge variant="secondary">Coming soon</Badge> | ||
| <Badge variant="secondary">Beta</Badge> |
There was a problem hiding this comment.
[P2] Align the NestJS support status
This card now labels NestJS as Beta, but the linked NestJS guide still says the integration is experimental. Because this PR explicitly promotes the documented support level, please update the guide callout to Beta as well—or retain the existing status here—so users do not receive conflicting maturity guarantees.
There was a problem hiding this comment.
Changed to align both to "experimental" since we're unsure if we want to support this officially
Signed-off-by: Peter Wielander <peter.wielander@vercel.com>
Uh oh!
There was an error while loading. Please reload this page.
No backport to This commit builds directly on NestJS Vercel Build Output support (#2988) that only exists on To override, re-run the Backport to stable workflow manually via |
Note CI is failing due to
world.analyticsissue unrelated to this PR.This PR enables the Vercel production e2e suite against the NestJS workbench by adding a
nestentry to thee2e-vercel-prodmatrix in.github/workflows/tests.yml:Follow-up to #2988 (which added NestJS Vercel Build Output support). That PR proved a NestJS app runs on Vercel; this wires the
workbench/nestapp into the same prod e2e lane every other framework runs in.Why no other changes are needed
nest:packages/core/e2e/utils.tsalready carves outnestinhasStepSourceMaps()/hasWorkflowSourceMaps(), ande2e.test.ts/e2e-agent.test.ts(the only files the prod job runs) handle non-Next / non-agent apps through the generic World +.well-known/workflow/v1/*path.workbench/nestexposesPOST /api/test-direct-step-call, the full example workflow set, and theflow/webhook/manifestendpoints viaworkflow-nest build --vercel.vercel.jsonsetsWORKFLOW_PUBLIC_MANIFEST=1like the others.workbench-nestjs-workflow(root dirworkbench/nest, prod branchmain) is connected to this repo; its Git integration was reconnected recently, so this PR's preview deploy is the first fresh build.changeset statusclean).