Skip to content

Support step function serialization in "client" mode#924

Merged
TooTallNate merged 1 commit intomainfrom
02-03-support_step_function_serialization_in_client_mode
Feb 7, 2026
Merged

Support step function serialization in "client" mode#924
TooTallNate merged 1 commit intomainfrom
02-03-support_step_function_serialization_in_client_mode

Conversation

@TooTallNate
Copy link
Member

@TooTallNate TooTallNate commented Feb 3, 2026

Added support for step function serialization in client mode by setting the stepId property and registering step functions.

What changed?

  • Added a stepId property to step functions in registerStepFunction to support serialization
  • Modified the SWC plugin to call registerStepFunction() on step functions in client mode
  • Updated the client mode transformation to preserve step function bodies while also registering them
  • Updated the plugin specification documentation to reflect these changes
  • Added appropriate imports for registerStepFunction in client mode output

How to test?

  1. Create a workflow that passes step functions as arguments to other step functions
  2. Run the workflow in client mode
  3. Verify that step functions are properly serialized and can be passed between boundaries
  4. Check that step functions maintain their identity when passed as arguments or returned from other functions

Why make this change?

This change enables proper serialization of step functions in client mode. Previously, step functions in client mode weren't registered, which meant they couldn't be properly serialized when passed as arguments to start() or returned from other step functions. By setting the stepId property and registering step functions in client mode, we ensure consistent behavior between client and server modes when step functions are passed across boundaries.

@changeset-bot
Copy link

changeset-bot bot commented Feb 3, 2026

🦋 Changeset detected

Latest commit: cee25ef

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

This PR includes changesets to release 15 packages
Name Type
@workflow/core Patch
@workflow/swc-plugin Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/web-shared Patch
workflow Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/world-testing Patch
@workflow/nuxt 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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 490 0 38 528
✅ 💻 Local Development 418 0 62 480
✅ 📦 Local Production 418 0 62 480
✅ 🐘 Local Postgres 418 0 62 480
✅ 🪟 Windows 45 0 3 48
❌ 🌍 Community Worlds 29 163 12 204
✅ 📋 Other 123 0 21 144
Total 1941 163 260 2364

❌ Failed Tests

🌍 Community Worlds (163 failed)

mongodb (40 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • 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
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (40 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • 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
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • 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 (queue-based) - workflow and step endpoints respond to health check messages
  • 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
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (41 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • 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 (queue-based) - workflow and step endpoints respond to health check messages
  • 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
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • 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 44 0 4
✅ example 44 0 4
✅ express 44 0 4
✅ fastify 44 0 4
✅ hono 44 0 4
✅ nextjs-turbopack 47 0 1
✅ nextjs-webpack 47 0 1
✅ nitro 44 0 4
✅ nuxt 44 0 4
✅ sveltekit 44 0 4
✅ vite 44 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 45 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 40 3
✅ redis-dev 3 0 0
❌ redis 5 40 3
✅ starter-dev 3 0 0
❌ starter 3 42 3
✅ turso-dev 3 0 0
❌ turso 4 41 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 41 0 7
✅ e2e-local-postgres-nest-stable 41 0 7
✅ e2e-local-prod-nest-stable 41 0 7

📋 View full workflow run

@vercel
Copy link
Contributor

vercel bot commented Feb 3, 2026

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 Feb 7, 2026 7:18pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Feb 7, 2026 7:18pm
example-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-astro-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-express-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-fastify-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-hono-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-nitro-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-nuxt-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workbench-vite-workflow Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 7, 2026 7:18pm
workflow-nest Ready Ready Preview, Comment Feb 7, 2026 7:18pm
workflow-swc-playground Ready Ready Preview, Comment Feb 7, 2026 7:18pm

@TooTallNate TooTallNate marked this pull request as ready for review February 3, 2026 19:57
Copy link
Member Author

TooTallNate commented Feb 3, 2026

Copilot AI review requested due to automatic review settings February 3, 2026 20:40
Copy link
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 adds support for step function serialization in client mode by registering step functions and setting their stepId property. This enables step functions to be properly serialized when passed as arguments to start() or returned from other step functions.

Changes:

  • Modified the SWC plugin to call registerStepFunction() on step functions in client mode
  • Updated registerStepFunction in packages/core/src/private.ts to set the stepId property on functions for serialization support
  • Added a custom StepFunction reviver in getWorkflowRevivers that wraps deserialized step functions with the useStep wrapper when in workflow context, allowing them to be called directly from workflow code
  • Updated test fixtures to include registerStepFunction calls and necessary imports in client mode outputs
  • Added an E2E test and example code demonstrating step functions being passed as arguments to start()

Reviewed changes

Copilot reviewed 33 out of 33 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
packages/core/src/private.ts Added stepId property to StepFunction type and modified registerStepFunction to set it
packages/core/src/serialization.ts Added custom StepFunction reviver in getWorkflowRevivers that returns useStep wrapper in workflow context
packages/swc-plugin-workflow/transform/src/lib.rs Modified client mode transformation to register step functions and added import generation
packages/swc-plugin-workflow/spec.md Updated documentation to reflect client mode step registration
workbench/example/workflows/99_e2e.ts Added test workflow and step functions for E2E testing
workbench/example/api/trigger.ts Added support for injecting step function references as test arguments
packages/core/e2e/e2e.test.ts Added E2E test for step function serialization
Multiple test fixtures Updated expected outputs to include registerStepFunction calls
.changeset/*.md Added changeset entries for the changes

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

@TooTallNate TooTallNate force-pushed the 02-03-support_step_function_serialization_in_client_mode branch from 2f41523 to cee25ef Compare February 7, 2026 19:15
@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2026

📊 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 🥇 Express 0.026s (-18.8% 🟢) 1.004s (~) 0.978s 10 1.00x
💻 Local Nitro 0.032s (+21.5% 🔺) 1.004s (~) 0.972s 10 1.24x
💻 Local Next.js (Turbopack) 0.040s (+1.0%) 1.005s (~) 0.965s 10 1.52x
🐘 Postgres Nitro 0.140s (-68.2% 🟢) 1.013s (-1.2%) 0.873s 10 5.37x
🐘 Postgres Express 0.173s (-43.6% 🟢) 1.009s (-2.3%) 0.836s 10 6.65x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.786s (-9.6% 🟢) 2.388s (-10.0% 🟢) 1.602s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.826s (-17.5% 🟢) 2.554s (-10.0% 🟢) 1.728s 10 1.05x
▲ Vercel Nitro 0.887s (-6.4% 🟢) 2.760s (+7.0% 🔺) 1.874s 10 1.13x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.074s (-2.9%) 2.005s (~) 0.930s 10 1.00x
💻 Local Next.js (Turbopack) 1.101s (~) 2.005s (~) 0.904s 10 1.03x
💻 Local Nitro 1.105s (+2.9%) 2.005s (~) 0.900s 10 1.03x
🐘 Postgres Express 2.256s (+0.8%) 3.013s (~) 0.757s 10 2.10x
🐘 Postgres Nitro 2.470s (+6.2% 🔺) 3.014s (~) 0.545s 10 2.30x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.678s (-2.1%) 3.821s (-6.4% 🟢) 1.143s 10 1.00x
▲ Vercel Nitro 2.780s (+1.4%) 4.039s (+2.3%) 1.259s 10 1.04x
▲ Vercel Next.js (Turbopack) 2.801s (-0.9%) 3.955s (-3.6%) 1.154s 10 1.05x

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

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 10.562s (-2.5%) 11.021s (~) 0.458s 3 1.00x
💻 Local Next.js (Turbopack) 10.707s (~) 11.021s (~) 0.314s 3 1.01x
💻 Local Nitro 10.817s (+2.5%) 11.021s (~) 0.203s 3 1.02x
🐘 Postgres Nitro 20.342s (+0.6%) 21.060s (~) 0.718s 2 1.93x
🐘 Postgres Express 20.456s (+1.7%) 21.053s (~) 0.597s 2 1.94x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 19.520s (+1.1%) 21.320s (+5.3% 🔺) 1.800s 2 1.00x
▲ Vercel Next.js (Turbopack) 19.956s (-1.5%) 21.187s (-2.1%) 1.230s 2 1.02x
▲ Vercel Express 19.983s (-1.2%) 21.127s (-3.7%) 1.144s 2 1.02x

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

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 26.802s (-2.5%) 27.048s (-3.6%) 0.246s 3 1.00x
💻 Local Next.js (Turbopack) 27.161s (~) 28.051s (~) 0.889s 3 1.01x
💻 Local Nitro 27.458s (+2.6%) 28.048s (+3.7%) 0.590s 3 1.02x
🐘 Postgres Express 50.305s (~) 51.130s (~) 0.825s 2 1.88x
🐘 Postgres Nitro 50.392s (~) 51.127s (~) 0.736s 2 1.88x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 49.602s (-3.3%) 50.839s (-3.5%) 1.237s 2 1.00x
▲ Vercel Next.js (Turbopack) 50.457s (-3.9%) 51.889s (-4.7%) 1.432s 2 1.02x
▲ Vercel Express 51.941s (~) 52.982s (-1.2%) 1.041s 2 1.05x

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

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 55.697s (-2.7%) 56.099s (-3.4%) 0.401s 2 1.00x
💻 Local Next.js (Turbopack) 56.536s (~) 57.097s (~) 0.561s 2 1.02x
💻 Local Nitro 57.110s (+2.7%) 57.601s (+2.7%) 0.491s 2 1.03x
🐘 Postgres Nitro 100.340s (~) 101.245s (~) 0.905s 1 1.80x
🐘 Postgres Express 100.510s (~) 101.224s (+1.0%) 0.714s 1 1.80x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 104.752s (-2.6%) 106.051s (-3.2%) 1.299s 1 1.00x
▲ Vercel Nitro 105.366s (~) 107.231s (+0.8%) 1.865s 1 1.01x
▲ Vercel Express 107.446s (~) 108.516s (-0.8%) 1.070s 1 1.03x

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

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.364s (-2.8%) 2.005s (~) 0.641s 15 1.00x
💻 Local Nitro 1.416s (+5.2% 🔺) 2.006s (~) 0.589s 15 1.04x
💻 Local Next.js (Turbopack) 1.439s (+2.9%) 2.005s (~) 0.566s 15 1.06x
🐘 Postgres Nitro 2.399s (+2.5%) 3.014s (~) 0.615s 10 1.76x
🐘 Postgres Express 2.442s (+5.5% 🔺) 3.013s (~) 0.571s 10 1.79x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.926s (-4.4%) 4.660s (+1.9%) 1.735s 7 1.00x
▲ Vercel Nitro 3.194s (+12.9% 🔺) 4.537s (+8.8% 🔺) 1.343s 7 1.09x
▲ Vercel Next.js (Turbopack) 3.924s (+16.9% 🔺) 5.490s (+11.2% 🔺) 1.566s 6 1.34x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 2.264s (-12.0% 🟢) 3.007s (~) 0.744s 10 1.00x
💻 Local Nitro 2.573s (+14.2% 🔺) 3.007s (~) 0.434s 10 1.14x
💻 Local Next.js (Turbopack) 2.582s (+4.4%) 3.007s (~) 0.425s 10 1.14x
🐘 Postgres Nitro 8.428s (+14.2% 🔺) 8.780s (+9.4% 🔺) 0.351s 4 3.72x
🐘 Postgres Express 9.486s (+11.9% 🔺) 10.034s (+11.1% 🔺) 0.548s 3 4.19x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.139s (-17.1% 🟢) 4.080s (-23.3% 🟢) 0.940s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.348s (-30.6% 🟢) 4.921s (-23.5% 🟢) 1.573s 7 1.07x
▲ Vercel Nitro 3.448s (-9.0% 🟢) 4.700s (-13.8% 🟢) 1.253s 7 1.10x

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

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 6.274s (-13.9% 🟢) 7.013s (-12.6% 🟢) 0.739s 5 1.00x
💻 Local Next.js (Turbopack) 6.877s (-1.6%) 7.416s (-4.5%) 0.539s 5 1.10x
💻 Local Nitro 7.179s (+11.3% 🔺) 7.771s (+10.8% 🔺) 0.592s 4 1.14x
🐘 Postgres Nitro 46.457s (+5.7% 🔺) 47.114s (+6.8% 🔺) 0.657s 1 7.40x
🐘 Postgres Express 50.619s (+9.0% 🔺) 51.116s (+8.5% 🔺) 0.497s 1 8.07x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 5.332s (+9.8% 🔺) 6.845s (+1.2%) 1.513s 5 1.00x
▲ Vercel Next.js (Turbopack) 6.969s (+10.2% 🔺) 8.608s (+6.6% 🔺) 1.639s 4 1.31x
▲ Vercel Express 7.277s (+114.1% 🔺) 8.272s (+63.1% 🔺) 0.995s 4 1.36x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.376s (-3.4%) 2.004s (~) 0.629s 15 1.00x
💻 Local Nitro 1.399s (+0.8%) 2.004s (~) 0.605s 15 1.02x
💻 Local Next.js (Turbopack) 1.416s (-1.1%) 2.005s (~) 0.589s 15 1.03x
🐘 Postgres Nitro 2.102s (+11.5% 🔺) 2.597s (+3.4%) 0.495s 12 1.53x
🐘 Postgres Express 2.133s (+2.2%) 2.595s (-5.4% 🟢) 0.462s 12 1.55x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 8.309s (+190.4% 🔺) 9.555s (+136.6% 🔺) 1.246s 4 1.00x
▲ Vercel Nitro 10.590s (+286.2% 🔺) 12.117s (+199.4% 🔺) 1.527s 3 1.27x
▲ Vercel Next.js (Turbopack) 12.175s (+299.5% 🔺) 13.496s (+206.2% 🔺) 1.321s 3 1.47x

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

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 2.479s (-8.9% 🟢) 3.007s (~) 0.528s 10 1.00x
💻 Local Next.js (Turbopack) 2.515s (-5.4% 🟢) 3.007s (~) 0.492s 10 1.01x
💻 Local Nitro 2.688s (+9.9% 🔺) 3.006s (~) 0.318s 10 1.08x
🐘 Postgres Nitro 10.606s (-9.0% 🟢) 11.361s (-5.6% 🟢) 0.755s 3 4.28x
🐘 Postgres Express 12.147s (+16.5% 🔺) 13.039s (+18.2% 🔺) 0.892s 3 4.90x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.017s (-47.8% 🟢) 4.244s (-42.0% 🟢) 1.226s 8 1.00x
▲ Vercel Express 3.152s (-31.5% 🟢) 4.116s (-35.6% 🟢) 0.964s 8 1.04x
▲ Vercel Nitro 3.922s (-23.6% 🟢) 5.358s (-16.3% 🟢) 1.435s 6 1.30x

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

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.333s (-7.4% 🟢) 8.018s (-3.1%) 0.684s 4 1.00x
💻 Local Next.js (Turbopack) 7.683s (-3.4%) 8.013s (-5.9% 🟢) 0.330s 4 1.05x
💻 Local Nitro 7.751s (+10.6% 🔺) 8.022s (+8.2% 🔺) 0.271s 4 1.06x
🐘 Postgres Nitro 50.836s (-4.6%) 51.112s (-5.5% 🟢) 0.276s 1 6.93x
🐘 Postgres Express 52.327s (+4.3%) 53.100s (+3.9%) 0.773s 1 7.14x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.357s (-64.5% 🟢) 5.385s (-51.6% 🟢) 2.029s 6 1.00x
▲ Vercel Express 3.784s (-48.0% 🟢) 5.187s (-39.9% 🟢) 1.403s 6 1.13x
▲ Vercel Nitro 4.435s (-44.0% 🟢) 5.609s (-40.0% 🟢) 1.175s 6 1.32x

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

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 0.116s (-32.8% 🟢) 1.002s (~) 0.009s (-15.8% 🟢) 1.013s (~) 0.897s 10 1.00x
💻 Local Next.js (Turbopack) 0.141s (-2.5%) 1.001s (~) 0.010s (-5.6% 🟢) 1.015s (~) 0.874s 10 1.22x
💻 Local Nitro 0.171s (+52.6% 🔺) 1.002s (~) 0.010s (+8.5% 🔺) 1.015s (~) 0.844s 10 1.47x
🐘 Postgres Express 2.147s (-8.9% 🟢) 2.895s (+7.9% 🔺) 0.001s (-8.3% 🟢) 3.014s (~) 0.867s 10 18.48x
🐘 Postgres Nitro 2.452s (+2.4%) 2.590s (-2.2%) 0.001s (-15.4% 🟢) 3.014s (~) 0.562s 10 21.10x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.803s (+3.1%) 3.346s (+6.2% 🔺) 0.168s (-38.5% 🟢) 4.378s (~) 1.575s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.893s (+6.9% 🔺) 3.221s (+1.2%) 0.203s (+45.1% 🔺) 4.336s (+2.7%) 1.443s 10 1.03x
▲ Vercel Express 3.186s (+18.0% 🔺) 3.631s (+6.7% 🔺) 0.221s (+57.7% 🔺) 4.679s (+6.2% 🔺) 1.493s 10 1.14x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Express 12/12
🐘 Postgres Nitro 9/12
▲ Vercel Express 5/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 11/12
Next.js (Turbopack) 💻 Local 11/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 merged commit fcfaf8b into main Feb 7, 2026
97 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants