Skip to content

Make wf build --manifest-file include steps / classes metadata#931

Merged
TooTallNate merged 1 commit intomainfrom
02-04-make_wf_build_--manifest-file_include_steps___classes_metadata
Feb 4, 2026
Merged

Make wf build --manifest-file include steps / classes metadata#931
TooTallNate merged 1 commit intomainfrom
02-04-make_wf_build_--manifest-file_include_steps___classes_metadata

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate commented Feb 4, 2026 •
edited
Loading

Updated the manifest file output to include complete workflow metadata instead of just the workflows object.

What changed?

  • Modified base-builder.ts to write the entire workflow manifest to the manifest file, not just the workflows property
  • Updated the workbench example trigger API to access workflows through the new structure (workflowManifest.workflows instead of directly from workflowManifest)

How to test?

  1. Run wf build --manifest-file=path/to/manifest.js
  2. Verify that the generated manifest file contains the complete workflow metadata including steps and classes
  3. Test the workbench example to ensure it correctly accesses workflows through the updated structure

Why make this change?

Including the complete workflow metadata (steps and classes) in the manifest file provides more comprehensive information for tools and services that consume this data. This enables better workflow visualization, debugging, and integration capabilities.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 4, 2026

🦋 Changeset detected

Latest commit: 0be144c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages
Name Type
@workflow/builders Patch
@workflow/astro Patch
@workflow/cli Patch
@workflow/nest Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
workflow Patch
@workflow/world-testing Patch
@workflow/docs-typecheck Patch
@workflow/nuxt Patch
@workflow/core Patch
@workflow/web-shared Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 4, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
example-nextjs-workflow-webpack Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
example-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-astro-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-express-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-fastify-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-hono-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-nitro-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-nuxt-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-sveltekit-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workbench-vite-workflow Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am
workflow-nest Ready Ready Preview, Comment, Open in v0 Feb 4, 2026 8:17am

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 4, 2026 •
edited
Loading

🧪 E2E Test Results

❌ Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 479 0 38 517
✅ 💻 Local Development 438 0 32 470
✅ 📦 Local Production 438 0 32 470
✅ 🐘 Local Postgres 438 0 32 470
✅ 🪟 Windows 47 0 0 47
❌ 🌍 Community Worlds 31 169 0 200
✅ 📋 Other 129 0 12 141
Total 2000 169 146 2315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 43 0 4
✅ example 43 0 4
✅ express 43 0 4
✅ fastify 43 0 4
✅ hono 43 0 4
✅ nextjs-turbopack 46 0 1
✅ nextjs-webpack 46 0 1
✅ nitro 43 0 4
✅ nuxt 43 0 4
✅ sveltekit 43 0 4
✅ vite 43 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 47 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 42 0
✅ redis-dev 3 0 0
❌ redis 5 42 0
✅ starter-dev 3 0 0
❌ starter 4 43 0
✅ turso-dev 3 0 0
❌ turso 5 42 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 43 0 4
✅ e2e-local-postgres-nest-stable 43 0 4
✅ e2e-local-prod-nest-stable 43 0 4

📋 View full workflow run

@TooTallNate Graphite App
Copy link
Copy Markdown
Member Author

TooTallNate commented Feb 4, 2026

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 4, 2026 •
edited
Loading

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.042s (-27.5% 🟢) 1.007s (~) 0.966s 10 1.00x
💻 Local Next.js (Turbopack) 0.042s (-0.7%) 1.019s (~) 0.978s 10 1.00x
💻 Local Express 0.043s (-1.1%) 1.008s (~) 0.964s 10 1.04x
🐘 Postgres Next.js (Turbopack) 0.180s (+7.4% 🔺) 1.023s (~) 0.843s 10 4.31x
🐘 Postgres Express 0.257s (-44.5% 🟢) 1.015s (-2.8%) 0.757s 10 6.17x
🐘 Postgres Nitro 0.265s (+23.5% 🔺) 1.014s (~) 0.750s 10 6.34x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.606s (-6.2% 🟢) 1.721s (+17.9% 🔺) 1.115s 10 1.00x
▲ Vercel Express 0.616s (-11.7% 🟢) 1.512s (-3.2%) 0.896s 10 1.02x
▲ Vercel Next.js (Turbopack) 0.617s (-10.5% 🟢) 1.480s (-4.3%) 0.863s 10 1.02x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.089s (~) 2.013s (~) 0.924s 10 1.00x
💻 Local Nitro 1.112s (-0.6%) 2.007s (~) 0.895s 10 1.02x
💻 Local Express 1.117s (~) 2.008s (~) 0.891s 10 1.03x
🐘 Postgres Next.js (Turbopack) 1.901s (~) 2.120s (~) 0.219s 10 1.75x
🐘 Postgres Nitro 2.130s (-5.8% 🟢) 3.015s (~) 0.885s 10 1.96x
🐘 Postgres Express 2.151s (-9.1% 🟢) 3.015s (~) 0.864s 10 1.98x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.762s (-1.9%) 3.663s (+1.4%) 0.901s 10 1.00x
▲ Vercel Express 2.949s (+3.4%) 3.627s (~) 0.678s 10 1.07x
▲ Vercel Next.js (Turbopack) 3.025s (+4.0%) 3.882s (+8.1% 🔺) 0.857s 10 1.10x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.713s (~) 11.019s (~) 0.306s 3 1.00x
💻 Local Nitro 10.814s (~) 11.012s (~) 0.199s 3 1.01x
💻 Local Express 10.851s (~) 11.016s (~) 0.165s 3 1.01x
🐘 Postgres Next.js (Turbopack) 15.287s (~) 16.041s (~) 0.754s 2 1.43x
🐘 Postgres Express 20.508s (+1.0%) 21.032s (~) 0.524s 2 1.91x
🐘 Postgres Nitro 20.530s (~) 21.029s (~) 0.499s 2 1.92x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 21.747s (-1.7%) 22.362s (-1.5%) 0.615s 2 1.00x
▲ Vercel Next.js (Turbopack) 22.387s (-0.6%) 23.359s (~) 0.972s 2 1.03x
▲ Vercel Express 22.769s (+1.1%) 23.812s (+1.9%) 1.043s 2 1.05x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.190s (~) 28.042s (~) 0.852s 3 1.00x
💻 Local Nitro 27.417s (~) 28.024s (~) 0.607s 3 1.01x
💻 Local Express 27.491s (~) 28.027s (~) 0.537s 3 1.01x
🐘 Postgres Next.js (Turbopack) 37.651s (~) 38.075s (~) 0.424s 2 1.38x
🐘 Postgres Express 50.400s (~) 51.083s (~) 0.684s 2 1.85x
🐘 Postgres Nitro 50.535s (+3.4%) 51.058s (+3.0%) 0.522s 2 1.86x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 56.092s (~) 56.942s (~) 0.851s 2 1.00x
▲ Vercel Next.js (Turbopack) 57.757s (+3.1%) 58.747s (+3.5%) 0.990s 2 1.03x
▲ Vercel Nitro 67.241s (+20.1% 🔺) 68.311s (+20.3% 🔺) 1.070s 1 1.20x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.673s (~) 57.047s (~) 0.373s 2 1.00x
💻 Local Nitro 57.068s (~) 57.549s (-0.9%) 0.481s 2 1.01x
💻 Local Express 57.336s (~) 58.057s (~) 0.721s 2 1.01x
🐘 Postgres Next.js (Turbopack) 75.722s (~) 76.125s (~) 0.403s 2 1.34x
🐘 Postgres Nitro 99.970s (+32.1% 🔺) 100.132s (+30.7% 🔺) 0.162s 1 1.76x
🐘 Postgres Express 100.179s (~) 101.156s (~) 0.977s 1 1.77x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 118.431s (+3.0%) 118.933s (+2.7%) 0.502s 1 1.00x
▲ Vercel Next.js (Turbopack) 121.744s (+3.5%) 122.396s (+2.9%) 0.652s 1 1.03x
▲ Vercel Express 121.752s (~) 123.092s (+0.9%) 1.340s 1 1.03x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.403s (~) 2.012s (~) 0.609s 15 1.00x
💻 Local Nitro 1.411s (+1.1%) 2.006s (~) 0.595s 15 1.01x
💻 Local Express 1.431s (+2.4%) 2.007s (~) 0.576s 15 1.02x
🐘 Postgres Next.js (Turbopack) 2.107s (+7.5% 🔺) 2.607s (+11.8% 🔺) 0.501s 12 1.50x
🐘 Postgres Nitro 2.137s (-3.9%) 3.014s (+10.1% 🔺) 0.877s 10 1.52x
🐘 Postgres Express 2.309s (+3.6%) 3.013s (~) 0.704s 10 1.65x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.116s (+7.9% 🔺) 3.829s (+1.3%) 0.713s 8 1.00x
▲ Vercel Nitro 3.178s (+7.2% 🔺) 4.082s (+9.9% 🔺) 0.905s 8 1.02x
▲ Vercel Express 3.441s (+12.1% 🔺) 4.109s (+3.7%) 0.669s 8 1.10x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.520s (+2.6%) 3.012s (~) 0.492s 10 1.00x
💻 Local Next.js (Turbopack) 2.604s (+2.1%) 3.019s (-2.9%) 0.414s 10 1.03x
💻 Local Express 2.618s (+5.8% 🔺) 3.021s (~) 0.402s 10 1.04x
🐘 Postgres Express 7.898s (-6.2% 🟢) 8.816s (-2.9%) 0.918s 4 3.13x
🐘 Postgres Nitro 8.616s (-9.9% 🟢) 9.314s (-7.0% 🟢) 0.698s 4 3.42x
🐘 Postgres Next.js (Turbopack) 11.221s (+4.1%) 12.029s (+5.6% 🔺) 0.808s 3 4.45x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.467s (+3.2%) 4.111s (+2.7%) 0.644s 8 1.00x
▲ Vercel Express 3.651s (+8.7% 🔺) 4.330s (-9.0% 🟢) 0.679s 7 1.05x
▲ Vercel Next.js (Turbopack) 3.785s (+19.4% 🔺) 4.500s (+18.6% 🔺) 0.715s 7 1.09x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 6.975s (+4.3%) 7.557s (~) 0.582s 4 1.00x
💻 Local Next.js (Turbopack) 7.166s (+3.1%) 8.549s (+11.7% 🔺) 1.383s 4 1.03x
💻 Local Express 7.465s (+11.6% 🔺) 8.464s (+10.7% 🔺) 0.999s 4 1.07x
🐘 Postgres Express 48.711s (+3.1%) 49.218s (+1.9%) 0.507s 1 6.98x
🐘 Postgres Nitro 49.024s (+1.7%) 49.363s (~) 0.339s 1 7.03x
🐘 Postgres Next.js (Turbopack) 51.123s (-3.5%) 52.134s (-2.0%) 1.011s 1 7.33x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.905s (+6.2% 🔺) 4.459s (+7.5% 🔺) 0.555s 7 1.00x
▲ Vercel Express 4.296s (+22.3% 🔺) 4.869s (+15.3% 🔺) 0.574s 7 1.10x
▲ Vercel Nitro 4.486s (+2.6%) 5.146s (+0.8%) 0.659s 6 1.15x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.436s (~) 2.005s (~) 0.569s 15 1.00x
💻 Local Next.js (Turbopack) 1.438s (+1.3%) 2.009s (~) 0.571s 15 1.00x
💻 Local Express 1.451s (+1.8%) 2.007s (~) 0.556s 15 1.01x
🐘 Postgres Nitro 1.655s (-25.3% 🟢) 2.010s (-25.0% 🟢) 0.355s 15 1.15x
🐘 Postgres Next.js (Turbopack) 2.040s (-9.9% 🟢) 2.481s (-12.7% 🟢) 0.441s 13 1.42x
🐘 Postgres Express 2.093s (-10.5% 🟢) 2.524s (-7.9% 🟢) 0.431s 12 1.46x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.717s (-5.5% 🟢) 3.654s (-2.7%) 0.937s 9 1.00x
▲ Vercel Next.js (Turbopack) 2.759s (~) 3.615s (-0.6%) 0.856s 9 1.02x
▲ Vercel Nitro 3.604s (+16.8% 🔺) 4.553s (+15.1% 🔺) 0.949s 7 1.33x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.634s (+1.0%) 3.009s (~) 0.375s 10 1.00x
💻 Local Next.js (Turbopack) 2.719s (+3.5%) 3.018s (~) 0.299s 10 1.03x
💻 Local Express 2.777s (+7.9% 🔺) 3.023s (~) 0.246s 10 1.05x
🐘 Postgres Nitro 9.782s (-27.5% 🟢) 10.027s (-28.5% 🟢) 0.245s 4 3.71x
🐘 Postgres Express 11.969s (-4.4%) 12.360s (-5.1% 🟢) 0.391s 3 4.54x
🐘 Postgres Next.js (Turbopack) 12.623s (-3.8%) 13.043s (-4.8%) 0.420s 3 4.79x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.175s (+8.0% 🔺) 3.985s (+10.0% 🔺) 0.811s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.335s (+19.4% 🔺) 4.049s (+12.0% 🔺) 0.714s 8 1.05x
▲ Vercel Express 3.495s (+24.6% 🔺) 4.352s (+21.6% 🔺) 0.857s 7 1.10x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 7.406s (-1.4%) 8.317s (-1.1%) 0.911s 4 1.00x
💻 Local Nitro 7.593s (~) 8.579s (~) 0.987s 4 1.03x
💻 Local Express 8.421s (+15.3% 🔺) 9.279s (+15.6% 🔺) 0.858s 4 1.14x
🐘 Postgres Express 48.014s (-4.1%) 48.283s (-3.8%) 0.269s 1 6.48x
🐘 Postgres Nitro 48.321s (-14.5% 🟢) 49.175s (-13.9% 🟢) 0.854s 1 6.52x
🐘 Postgres Next.js (Turbopack) 52.128s (-10.6% 🟢) 52.834s (-10.8% 🟢) 0.706s 1 7.04x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.334s (-13.0% 🟢) 3.812s (-16.2% 🟢) 0.478s 8 1.00x
▲ Vercel Nitro 3.789s (+9.2% 🔺) 4.436s (+8.6% 🔺) 0.647s 7 1.14x
▲ Vercel Next.js (Turbopack) 3.941s (+8.3% 🔺) 5.140s (+22.1% 🔺) 1.198s 6 1.18x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.145s (+4.0%) 1.003s (~) 0.016s (+2.6%) 1.026s (~) 0.881s 10 1.00x
💻 Local Nitro 0.179s (-4.5%) 0.993s (~) 0.013s (+8.0% 🔺) 1.020s (~) 0.841s 10 1.24x
💻 Local Express 0.186s (-2.2%) 0.992s (~) 0.015s (+16.8% 🔺) 1.022s (~) 0.835s 10 1.29x
🐘 Postgres Next.js (Turbopack) 0.664s (-42.6% 🟢) 0.917s (-51.4% 🟢) 0.000s (NaN%) 1.017s (-49.6% 🟢) 0.353s 10 4.59x
🐘 Postgres Nitro 1.203s (-10.4% 🟢) 1.840s (+8.4% 🔺) 0.000s (NaN%) 2.013s (~) 0.810s 10 8.31x
🐘 Postgres Express 2.373s (+2.9%) 2.671s (-2.4%) 0.000s (-66.7% 🟢) 3.016s (~) 0.643s 10 16.40x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.004s (-2.7%) 3.357s (+3.3%) 0.108s (-54.2% 🟢) 3.971s (~) 0.967s 10 1.00x
▲ Vercel Nitro 3.041s (+3.4%) 3.237s (+1.8%) 0.203s (+33.5% 🔺) 4.020s (+6.0% 🔺) 0.979s 10 1.01x
▲ Vercel Express 3.224s (+8.7% 🔺) 3.281s (+3.2%) 0.154s (+1.0%) 4.024s (+5.4% 🔺) 0.800s 10 1.07x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 7/12
🐘 Postgres Next.js (Turbopack) 7/12
▲ Vercel Nitro 6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 10/12
Nitro 💻 Local 10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

@TooTallNate TooTallNate marked this pull request as ready for review February 4, 2026 08:16
Copilot AI reviewed Feb 4, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR modifies the wf build --manifest-file output to include the complete workflow metadata (steps, workflows, and classes) instead of only the workflows object. This provides consumers with comprehensive information for workflow visualization, debugging, and integration.

Changes:

  • Modified base-builder.ts to write the entire WorkflowManifest object to the manifest file instead of just the workflows property
  • Updated workbench/example/api/trigger.ts to access workflows through workflowManifest.workflows instead of directly from the root
  • Added a changeset documenting this change as a patch version

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
packages/builders/src/base-builder.ts Changed manifest file output from workflowManifest.workflows to the complete workflowManifest object
workbench/example/api/trigger.ts Updated to access workflows via workflowManifest.workflows property path
.changeset/few-drinks-return.md Added changeset for this feature as a patch release

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .changeset/few-drinks-return.md
@TooTallNate TooTallNate merged commit 2453b29 into main Feb 4, 2026
104 checks passed
@TooTallNate TooTallNate deleted the 02-04-make_wf_build_--manifest-file_include_steps___classes_metadata branch February 4, 2026 17:22
@vercel-release-bot vercel-release-bot mentioned this pull request Feb 4, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@ijjk ijjk ijjk approved these changes

@pranaygp pranaygp Awaiting requested review from pranaygp

@VaguelySerious VaguelySerious Awaiting requested review from VaguelySerious

@karthikscale3 karthikscale3 Awaiting requested review from karthikscale3

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@TooTallNate @ijjk