Skip to content

[core] Refactor getWorld interface to be asynchronous#942

Open
VaguelySerious wants to merge 9 commits intomainfrom
peter/async-world
Open

[core] Refactor getWorld interface to be asynchronous#942
VaguelySerious wants to merge 9 commits intomainfrom
peter/async-world

Conversation

@VaguelySerious
Copy link
Member

@VaguelySerious VaguelySerious commented Feb 5, 2026

This is based on community PR #836 which highlighted the need for an asynchronous interface so that we can use ESM dynamic imports.

Fixes #812

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@changeset-bot
Copy link

changeset-bot bot commented Feb 5, 2026

🦋 Changeset detected

Latest commit: 1871507

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/builders Patch
@workflow/cli Patch
@workflow/docs-typecheck 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

@vercel
Copy link
Contributor

vercel bot commented Feb 5, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 479 0 38 517
❌ 💻 Local Development 436 2 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 1998 171 146 2315

❌ Failed Tests

💻 Local Development (2 failed)

astro-stable (2 failed):

  • 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
🌍 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 41 2 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


Some E2E test jobs failed:

  • Vercel Prod: success
  • Local Dev: failure
  • Local Prod: success
  • Local Postgres: success
  • Windows: success

Check the workflow run for details.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 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 🥇 Next.js (Turbopack) 0.038s (-10.6% 🟢) 1.016s (~) 0.978s 10 1.00x
💻 Local Nitro 0.043s (-1.6%) 1.008s (~) 0.965s 10 1.13x
💻 Local Express 0.045s (-1.5%) 1.008s (~) 0.963s 10 1.19x
🐘 Postgres Nitro 0.146s (-22.6% 🟢) 1.014s (~) 0.868s 10 3.87x
🐘 Postgres Express 0.236s (-0.5%) 1.016s (~) 0.780s 10 6.23x
🐘 Postgres Next.js (Turbopack) 0.369s (+78.9% 🔺) 1.021s (~) 0.652s 10 9.75x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.610s (-24.1% 🟢) 1.574s (-3.5%) 0.964s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.663s (-1.5%) 1.617s (-7.8% 🟢) 0.954s 10 1.09x
▲ Vercel Nitro 0.665s (-44.7% 🟢) 1.805s (-3.9%) 1.140s 10 1.09x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.097s (~) 2.012s (~) 0.914s 10 1.00x
💻 Local Nitro 1.117s (~) 2.007s (~) 0.889s 10 1.02x
💻 Local Express 1.119s (~) 2.007s (~) 0.888s 10 1.02x
🐘 Postgres Express 2.259s (~) 3.015s (~) 0.757s 10 2.06x
🐘 Postgres Next.js (Turbopack) 2.270s (+27.8% 🔺) 3.017s (+42.5% 🔺) 0.747s 10 2.07x
🐘 Postgres Nitro 2.451s (+3.9%) 3.013s (~) 0.562s 10 2.23x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.695s (~) 3.552s (-5.9% 🟢) 0.857s 10 1.00x
▲ Vercel Nitro 2.798s (+2.5%) 3.831s (+6.0% 🔺) 1.033s 10 1.04x
▲ Vercel Express 3.001s (+10.3% 🔺) 4.092s (+11.1% 🔺) 1.091s 10 1.11x

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

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.719s (~) 11.019s (~) 0.301s 3 1.00x
💻 Local Nitro 10.842s (~) 11.016s (~) 0.174s 3 1.01x
💻 Local Express 10.867s (~) 11.013s (~) 0.147s 3 1.01x
🐘 Postgres Next.js (Turbopack) 20.161s (+32.8% 🔺) 21.035s (+35.4% 🔺) 0.874s 2 1.88x
🐘 Postgres Nitro 20.375s (~) 21.032s (~) 0.657s 2 1.90x
🐘 Postgres Express 20.436s (~) 21.035s (~) 0.600s 2 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 20.747s (-2.0%) 21.624s (-2.3%) 0.877s 2 1.00x
▲ Vercel Express 20.797s (-3.2%) 21.623s (-2.5%) 0.826s 2 1.00x
▲ Vercel Nitro 21.962s (+2.3%) 22.444s (+2.2%) 0.482s 2 1.06x

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

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.156s (~) 28.025s (~) 0.869s 3 1.00x
💻 Local Nitro 27.508s (~) 28.021s (~) 0.513s 3 1.01x
💻 Local Express 27.533s (~) 28.027s (~) 0.493s 3 1.01x
🐘 Postgres Express 50.294s (~) 51.089s (~) 0.794s 2 1.85x
🐘 Postgres Next.js (Turbopack) 50.307s (+33.2% 🔺) 51.102s (+34.3% 🔺) 0.795s 2 1.85x
🐘 Postgres Nitro 50.376s (~) 51.053s (~) 0.677s 2 1.86x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 53.268s (-1.2%) 54.189s (-1.1%) 0.921s 2 1.00x
▲ Vercel Express 53.398s (-1.1%) 54.536s (~) 1.138s 2 1.00x
▲ Vercel Next.js (Turbopack) 54.460s (-1.5%) 55.639s (~) 1.179s 2 1.02x

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

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.581s (~) 57.055s (~) 0.473s 2 1.00x
💻 Local Express 57.257s (~) 58.037s (~) 0.780s 2 1.01x
💻 Local Nitro 57.302s (~) 58.057s (~) 0.755s 2 1.01x
🐘 Postgres Nitro 100.304s (~) 101.122s (~) 0.818s 1 1.77x
🐘 Postgres Next.js (Turbopack) 100.320s (+50.9% 🔺) 101.175s (+50.8% 🔺) 0.855s 1 1.77x
🐘 Postgres Express 100.551s (~) 101.125s (~) 0.574s 1 1.78x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 109.420s (-5.9% 🟢) 109.912s (-5.7% 🟢) 0.492s 1 1.00x
▲ Vercel Nitro 112.416s (-2.7%) 113.297s (-2.3%) 0.881s 1 1.03x
▲ Vercel Next.js (Turbopack) 113.442s (+1.4%) 114.466s (+2.0%) 1.024s 1 1.04x

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

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.389s (~) 2.011s (~) 0.622s 15 1.00x
💻 Local Express 1.404s (~) 2.007s (~) 0.603s 15 1.01x
💻 Local Nitro 1.415s (-1.1%) 2.007s (~) 0.592s 15 1.02x
🐘 Postgres Express 2.203s (~) 3.013s (~) 0.810s 10 1.59x
🐘 Postgres Nitro 2.425s (+12.4% 🔺) 3.011s (~) 0.586s 10 1.75x
🐘 Postgres Next.js (Turbopack) 2.470s (+26.6% 🔺) 3.016s (+35.3% 🔺) 0.546s 10 1.78x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.715s (-4.7%) 3.701s (-1.6%) 0.987s 9 1.00x
▲ Vercel Nitro 2.865s (-2.8%) 3.878s (~) 1.013s 8 1.06x
▲ Vercel Next.js (Turbopack) 3.151s (+12.4% 🔺) 3.902s (+2.2%) 0.751s 8 1.16x

🔍 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 🥇 Next.js (Turbopack) 2.478s (-4.4%) 3.076s (+1.8%) 0.598s 10 1.00x
💻 Local Express 2.569s (-1.1%) 3.014s (~) 0.445s 10 1.04x
💻 Local Nitro 2.612s (-1.2%) 3.019s (~) 0.407s 10 1.05x
🐘 Postgres Express 9.248s (+6.9% 🔺) 9.581s (+2.8%) 0.334s 4 3.73x
🐘 Postgres Nitro 9.369s (+16.9% 🔺) 9.789s (+11.2% 🔺) 0.419s 4 3.78x
🐘 Postgres Next.js (Turbopack) 12.003s (-1.0%) 12.696s (~) 0.693s 3 4.84x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.000s (-0.8%) 3.792s (-2.4%) 0.792s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.451s (-11.4% 🟢) 4.749s (+0.9%) 1.298s 7 1.15x
▲ Vercel Nitro 3.986s (+26.0% 🔺) 4.658s (+20.6% 🔺) 0.672s 7 1.33x

🔍 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 🥇 Next.js (Turbopack) 6.383s (-8.3% 🟢) 6.838s (-17.5% 🟢) 0.455s 5 1.00x
💻 Local Nitro 7.322s (-5.8% 🟢) 8.329s (-4.8%) 1.006s 4 1.15x
💻 Local Express 7.422s (+1.6%) 8.418s (+3.9%) 0.996s 4 1.16x
🐘 Postgres Express 43.144s (-2.0%) 43.511s (-1.8%) 0.367s 1 6.76x
🐘 Postgres Nitro 51.805s (+21.4% 🔺) 52.096s (+20.7% 🔺) 0.291s 1 8.12x
🐘 Postgres Next.js (Turbopack) 52.556s (-5.8% 🟢) 53.193s (-5.3% 🟢) 0.637s 1 8.23x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 6.045s (+40.3% 🔺) 6.876s (+36.4% 🔺) 0.831s 5 1.00x
▲ Vercel Express 6.117s (+77.4% 🔺) 6.907s (+67.4% 🔺) 0.790s 5 1.01x
▲ Vercel Nitro 7.077s (+108.7% 🔺) 7.949s (+67.8% 🔺) 0.872s 4 1.17x

🔍 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 🥇 Express 1.440s (~) 2.007s (~) 0.567s 15 1.00x
💻 Local Nitro 1.455s (+1.0%) 2.007s (~) 0.552s 15 1.01x
💻 Local Next.js (Turbopack) 1.516s (+4.5%) 2.083s (+3.6%) 0.567s 15 1.05x
🐘 Postgres Express 2.109s (~) 2.513s (-6.4% 🟢) 0.404s 12 1.46x
🐘 Postgres Nitro 2.111s (+5.9% 🔺) 2.602s (+8.6% 🔺) 0.491s 12 1.47x
🐘 Postgres Next.js (Turbopack) 2.257s (+12.5% 🔺) 2.939s (+32.0% 🔺) 0.681s 11 1.57x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.664s (-1.1%) 3.666s (-2.8%) 1.002s 9 1.00x
▲ Vercel Express 2.694s (-4.4%) 3.664s (~) 0.969s 9 1.01x
▲ Vercel Nitro 3.186s (+7.7% 🔺) 4.163s (+7.0% 🔺) 0.977s 8 1.20x

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

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.577s (-6.0% 🟢) 3.031s (+0.6%) 0.454s 10 1.00x
💻 Local Nitro 2.693s (-4.6%) 3.013s (-1.2%) 0.320s 10 1.04x
💻 Local Express 2.729s (~) 3.018s (~) 0.288s 10 1.06x
🐘 Postgres Express 10.753s (-9.7% 🟢) 11.368s (-8.3% 🟢) 0.616s 3 4.17x
🐘 Postgres Nitro 12.427s (+26.7% 🔺) 13.059s (+25.4% 🔺) 0.632s 3 4.82x
🐘 Postgres Next.js (Turbopack) 13.949s (+11.8% 🔺) 14.377s (+13.1% 🔺) 0.429s 3 5.41x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.735s (-1.0%) 3.780s (+5.4% 🔺) 1.044s 8 1.00x
▲ Vercel Next.js (Turbopack) 2.769s (-5.6% 🟢) 3.663s (-2.2%) 0.893s 9 1.01x
▲ Vercel Express 2.811s (-4.6%) 3.664s (~) 0.853s 9 1.03x

🔍 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.509s (-4.5%) 8.887s (+2.0%) 1.378s 4 1.00x
💻 Local Express 7.619s (-3.6%) 8.579s (-3.1%) 0.961s 4 1.01x
💻 Local Nitro 7.919s (-1.8%) 8.876s (+1.9%) 0.957s 4 1.05x
🐘 Postgres Express 48.295s (-5.3% 🟢) 48.393s (-5.7% 🟢) 0.098s 1 6.43x
🐘 Postgres Nitro 53.402s (+7.6% 🔺) 54.090s (+7.9% 🔺) 0.688s 1 7.11x
🐘 Postgres Next.js (Turbopack) 54.474s (-4.3%) 55.202s (-3.7%) 0.728s 1 7.25x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 4.392s (+28.7% 🔺) 5.093s (+24.2% 🔺) 0.701s 7 1.00x
▲ Vercel Nitro 4.605s (+40.6% 🔺) 5.511s (+36.3% 🔺) 0.907s 7 1.05x
▲ Vercel Express 4.714s (+41.1% 🔺) 5.233s (+34.0% 🔺) 0.519s 6 1.07x

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

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.144s (-0.7%) 1.003s (~) 0.015s (-3.8%) 1.026s (~) 0.882s 10 1.00x
💻 Local Express 0.179s (-2.1%) 0.993s (~) 0.014s (-2.1%) 1.021s (~) 0.842s 10 1.25x
💻 Local Nitro 0.184s (-4.9%) 0.993s (~) 0.014s (-12.6% 🟢) 1.021s (~) 0.837s 10 1.28x
🐘 Postgres Next.js (Turbopack) 1.373s (+65.7% 🔺) 1.675s (+124.6% 🔺) 0.000s (NaN%) 2.020s (+99.1% 🔺) 0.646s 10 9.55x
🐘 Postgres Express 2.271s (-1.0%) 2.772s (+0.8%) 0.000s (+Infinity% 🔺) 3.016s (~) 0.745s 10 15.79x
🐘 Postgres Nitro 2.290s (~) 2.752s (~) 0.000s (NaN%) 3.015s (~) 0.725s 10 15.92x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.718s (-9.5% 🟢) 3.204s (-3.5%) 0.159s (+4.0%) 3.800s (-6.5% 🟢) 1.082s 10 1.00x
▲ Vercel Nitro 2.722s (+6.0% 🔺) 3.353s (+6.0% 🔺) 0.153s (+1.9%) 3.994s (+6.6% 🔺) 1.272s 10 1.00x
▲ Vercel Express 2.731s (-2.4%) 3.229s (-1.2%) 0.193s (+21.8% 🔺) 3.937s (+1.1%) 1.206s 10 1.00x

🔍 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) 11/12
🐘 Postgres Express 8/12
▲ Vercel Next.js (Turbopack) 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

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
This reverts commit 15193e8.
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.

@workflow/world-postgres: ERR_REQUIRE_ESM with Next.js 15

4 participants