Skip to content

[world-vercel] Update queue to use VQS v3 API#799

Merged
VaguelySerious merged 29 commits into
mainfrom
peter/vqs-v3
Jan 26, 2026
Merged

[world-vercel] Update queue to use VQS v3 API#799
VaguelySerious merged 29 commits into
mainfrom
peter/vqs-v3

Conversation

@VaguelySerious
Copy link
Copy Markdown
Member

@VaguelySerious VaguelySerious commented Jan 17, 2026

Updates VQS version inside world-vercel

Note this also moves to the new default visibilityTimeout (30s) and visibilityRefreshInterval (10s)

- Update basePath from /queues/v2/messages to /queues/v3
- Include @vercel/queue tarball with v3 client changes
- Add pnpm override to use bundled tarball

The @vercel/queue client has been updated to:
- Use v3 URL structure (topic and consumer in path)
- Use receiptHandle instead of ticket
- Support both v2 and v3 header names for backwards compat

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jan 17, 2026

🦋 Changeset detected

Latest commit: 40a7d16

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

This PR includes changesets to release 14 packages
Name Type
@workflow/world-vercel Patch
@workflow/cli Patch
@workflow/core Patch
@workflow/web-shared Patch
workflow Patch
@workflow/world-testing Patch
@workflow/builders Patch
@workflow/docs-typecheck Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/ai Patch
@workflow/astro Patch
@workflow/sveltekit 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
Copy Markdown
Contributor

vercel Bot commented Jan 17, 2026

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

Project Deployment Review Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Jan 26, 2026 2:01pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Jan 26, 2026 2:01pm
example-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-astro-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-express-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-fastify-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-hono-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-nitro-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-nuxt-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workbench-vite-workflow Ready Ready Preview, Comment Jan 26, 2026 2:01pm
workflow-docs Ready Ready Preview, Comment Jan 26, 2026 2:01pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 17, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 457 0 38 495
✅ 💻 Local Development 418 0 32 450
✅ 📦 Local Production 418 0 32 450
✅ 🐘 Local Postgres 418 0 32 450
✅ 🪟 Windows 45 0 0 45
❌ 🌍 Community Worlds 31 161 0 192
Total 1787 161 134 2082

❌ Failed Tests

🌍 Community Worlds (161 failed)

mongodb (40 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
  • 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
  • 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
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (41 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
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (40 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
  • 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 41 0 4
✅ example 41 0 4
✅ express 41 0 4
✅ fastify 41 0 4
✅ hono 41 0 4
✅ nextjs-turbopack 44 0 1
✅ nextjs-webpack 44 0 1
✅ nitro 41 0 4
✅ nuxt 41 0 4
✅ sveltekit 41 0 4
✅ vite 41 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 41 0 4
✅ express-stable 41 0 4
✅ fastify-stable 41 0 4
✅ hono-stable 41 0 4
✅ nextjs-turbopack-stable 45 0 0
✅ nextjs-webpack-stable 45 0 0
✅ nitro-stable 41 0 4
✅ nuxt-stable 41 0 4
✅ sveltekit-stable 41 0 4
✅ vite-stable 41 0 4
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 41 0 4
✅ express-stable 41 0 4
✅ fastify-stable 41 0 4
✅ hono-stable 41 0 4
✅ nextjs-turbopack-stable 45 0 0
✅ nextjs-webpack-stable 45 0 0
✅ nitro-stable 41 0 4
✅ nuxt-stable 41 0 4
✅ sveltekit-stable 41 0 4
✅ vite-stable 41 0 4
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 41 0 4
✅ express-stable 41 0 4
✅ fastify-stable 41 0 4
✅ hono-stable 41 0 4
✅ nextjs-turbopack-stable 45 0 0
✅ nextjs-webpack-stable 45 0 0
✅ nitro-stable 41 0 4
✅ nuxt-stable 41 0 4
✅ sveltekit-stable 41 0 4
✅ vite-stable 41 0 4
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 45 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 40 0
✅ redis-dev 3 0 0
❌ redis 5 40 0
✅ starter-dev 3 0 0
❌ starter 4 41 0
✅ turso-dev 3 0 0
❌ turso 5 40 0

📋 View full workflow run

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 17, 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.040s (-10.0% 🟢) 1.017s (~) 0.977s 10 1.00x
💻 Local Nitro 0.043s (-1.4%) 1.007s (~) 0.964s 10 1.07x
💻 Local Express 0.046s (~) 1.008s (~) 0.962s 10 1.15x
🐘 Postgres Nitro 0.237s (-6.5% 🟢) 1.015s (~) 0.778s 10 5.97x
🐘 Postgres Express 0.287s (-1.0%) 1.014s (~) 0.727s 10 7.23x
🐘 Postgres Next.js (Turbopack) 0.288s (+101.6% 🔺) 1.021s (~) 0.732s 10 7.27x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.634s (-28.6% 🟢) 1.799s (+2.0%) 1.164s 10 1.00x
▲ Vercel Nitro 0.638s (-19.4% 🟢) 1.749s (+3.4%) 1.112s 10 1.01x
▲ Vercel Next.js (Turbopack) 0.757s (~) 1.593s (-18.9% 🟢) 0.836s 10 1.19x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.091s (-0.8%) 2.012s (~) 0.921s 10 1.00x
💻 Local Nitro 1.115s (~) 2.006s (~) 0.891s 10 1.02x
💻 Local Express 1.117s (~) 2.007s (~) 0.889s 10 1.02x
🐘 Postgres Express 2.131s (~) 3.015s (~) 0.884s 10 1.95x
🐘 Postgres Nitro 2.177s (-0.6%) 3.015s (~) 0.838s 10 2.00x
🐘 Postgres Next.js (Turbopack) 2.287s (+17.9% 🔺) 2.917s (+37.8% 🔺) 0.631s 10 2.10x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.863s (-3.1%) 3.858s (+5.3% 🔺) 0.995s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.960s (+4.0%) 3.739s (+2.6%) 0.780s 10 1.03x
▲ Vercel Nitro 3.009s (+3.9%) 3.850s (+3.7%) 0.840s 10 1.05x

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

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.693s (~) 11.021s (~) 0.328s 5 1.00x
💻 Local Nitro 10.832s (~) 11.016s (~) 0.184s 5 1.01x
💻 Local Express 10.847s (~) 11.014s (~) 0.168s 5 1.01x
🐘 Postgres Next.js (Turbopack) 15.176s (-0.5%) 16.037s (~) 0.861s 5 1.42x
🐘 Postgres Express 20.069s (+12.3% 🔺) 20.429s (+12.0% 🔺) 0.360s 5 1.88x
🐘 Postgres Nitro 20.433s (~) 21.039s (~) 0.606s 5 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 23.488s (-6.8% 🟢) 24.547s (-4.9%) 1.058s 5 1.00x
▲ Vercel Nitro 23.718s (-10.0% 🟢) 24.706s (-8.3% 🟢) 0.988s 5 1.01x
▲ Vercel Next.js (Turbopack) 24.052s (-8.6% 🟢) 24.742s (-7.7% 🟢) 0.690s 5 1.02x

🔍 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.398s (~) 2.012s (~) 0.614s 15 1.00x
💻 Local Express 1.398s (-1.0%) 2.007s (~) 0.608s 15 1.00x
💻 Local Nitro 1.410s (+1.3%) 2.006s (~) 0.596s 15 1.01x
🐘 Postgres Next.js (Turbopack) 2.256s (+33.6% 🔺) 2.840s (+39.2% 🔺) 0.584s 11 1.61x
🐘 Postgres Nitro 2.262s (+2.6%) 3.017s (~) 0.754s 10 1.62x
🐘 Postgres Express 2.274s (+12.0% 🔺) 3.010s (+9.7% 🔺) 0.736s 10 1.63x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.067s (+2.5%) 3.861s (+6.2% 🔺) 0.794s 8 1.00x
▲ Vercel Express 3.201s (+10.6% 🔺) 4.059s (+10.9% 🔺) 0.858s 8 1.04x
▲ Vercel Nitro 3.442s (+10.2% 🔺) 4.344s (+11.6% 🔺) 0.902s 8 1.12x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.447s (-3.7%) 3.049s (+1.1%) 0.602s 10 1.00x
💻 Local Next.js (Turbopack) 2.483s (+2.9%) 3.175s (-6.0% 🟢) 0.693s 10 1.01x
💻 Local Express 2.486s (~) 3.016s (-0.6%) 0.529s 10 1.02x
🐘 Postgres Nitro 8.373s (-1.3%) 9.079s (~) 0.706s 4 3.42x
🐘 Postgres Express 9.206s (+3.9%) 9.789s (+2.5%) 0.583s 4 3.76x
🐘 Postgres Next.js (Turbopack) 13.258s (+20.7% 🔺) 13.688s (+17.1% 🔺) 0.430s 3 5.42x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.755s (+5.2% 🔺) 4.651s (+11.5% 🔺) 0.896s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.761s (+17.1% 🔺) 4.268s (+14.9% 🔺) 0.506s 8 1.00x
▲ Vercel Nitro 3.947s (+9.7% 🔺) 4.783s (+16.2% 🔺) 0.837s 7 1.05x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.405s (~) 2.005s (~) 0.601s 15 1.00x
💻 Local Next.js (Turbopack) 1.412s (+0.8%) 2.011s (~) 0.600s 15 1.00x
💻 Local Express 1.437s (+0.6%) 2.007s (~) 0.569s 15 1.02x
🐘 Postgres Nitro 1.904s (-5.9% 🟢) 2.406s (-10.3% 🟢) 0.502s 13 1.36x
🐘 Postgres Express 2.106s (-1.9%) 2.603s (~) 0.497s 12 1.50x
🐘 Postgres Next.js (Turbopack) 2.378s (+58.9% 🔺) 2.933s (+45.8% 🔺) 0.555s 11 1.69x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.765s (-4.1%) 3.853s (+2.6%) 1.088s 8 1.00x
▲ Vercel Nitro 2.849s (-3.9%) 3.829s (+2.9%) 0.980s 8 1.03x
▲ Vercel Next.js (Turbopack) 2.893s (~) 3.746s (~) 0.853s 9 1.05x

🔍 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 🥇 Nitro 2.546s (-3.9%) 3.017s (~) 0.471s 10 1.00x
💻 Local Express 2.593s (+0.5%) 3.026s (~) 0.433s 10 1.02x
💻 Local Next.js (Turbopack) 2.629s (+5.1% 🔺) 3.155s (+3.6%) 0.526s 10 1.03x
🐘 Postgres Nitro 11.226s (-1.4%) 11.736s (-2.7%) 0.510s 3 4.41x
🐘 Postgres Express 12.051s (+4.6%) 12.705s (+8.5% 🔺) 0.654s 3 4.73x
🐘 Postgres Next.js (Turbopack) 13.646s (+25.6% 🔺) 14.046s (+22.9% 🔺) 0.400s 3 5.36x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.080s (-2.4%) 3.951s (+4.6%) 0.871s 8 1.00x
▲ Vercel Express 3.357s (+7.7% 🔺) 4.360s (+20.6% 🔺) 1.003s 7 1.09x
▲ Vercel Next.js (Turbopack) 3.911s (+12.7% 🔺) 4.453s (+8.8% 🔺) 0.542s 7 1.27x

🔍 Observability: Nitro | Express | 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.143s (+2.8%) 1.003s (~) 0.016s (+1.9%) 1.027s (~) 0.884s 10 1.00x
💻 Local Nitro 0.180s (-4.6%) 0.992s (~) 0.015s (-9.4% 🟢) 1.022s (~) 0.842s 10 1.26x
💻 Local Express 0.184s (+1.5%) 0.993s (~) 0.015s (~) 1.023s (~) 0.839s 10 1.29x
🐘 Postgres Next.js (Turbopack) 1.257s (+2.7%) 1.576s (-13.4% 🟢) 0.000s (+200.0% 🔺) 1.818s (-10.1% 🟢) 0.561s 10 8.82x
🐘 Postgres Express 1.287s (-2.8%) 1.754s (-2.2%) 0.000s (+Infinity% 🔺) 2.013s (~) 0.726s 10 9.03x
🐘 Postgres Nitro 2.218s (-0.6%) 2.826s (+0.5%) 0.000s (+Infinity% 🔺) 3.017s (~) 0.799s 10 15.55x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.151s (+7.5% 🔺) 3.267s (+2.5%) 1.170s (+219.0% 🔺) 4.977s (+24.6% 🔺) 1.826s 10 1.00x
▲ Vercel Nitro 3.196s (+8.2% 🔺) 3.509s (+6.7% 🔺) 0.481s (+64.7% 🔺) 4.581s (+10.5% 🔺) 1.385s 10 1.01x
▲ Vercel Express 3.199s (+11.0% 🔺) 3.471s (+5.0% 🔺) 1.057s (+110.8% 🔺) 5.181s (+21.4% 🔺) 1.982s 10 1.02x

🔍 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) 5/8
🐘 Postgres Nitro 4/8
▲ Vercel Express 5/8
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 8/8
Next.js (Turbopack) 💻 Local 8/8
Nitro 💻 Local 8/8
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

- Use cgowrie/v3-client branch which has full v3 implementation
- Update basePath to /queues/v3/queues (matches new client default)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
VQS v3 uses /api/v3/topic/{topic} URL pattern instead of /api/v3/queues.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

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

🔧 Build Fix:

Type mismatch between two versions of @ai-sdk/provider library (v3.0.4 and v2.0.0) causing TypeScript compilation errors. The SharedV2ProviderMetadata type from v3.0.4 is incompatible with the v2.0.0 version expected by the codebase.

Fix on Vercel

VaguelySerious and others added 8 commits January 20, 2026 17:12
The receiveMessageById method was sending Accept: application/json which
the V3 server rejects. Updated tarball includes the fix to use
Accept: multipart/mixed and proper multipart response parsing.

Also cleaned up duplicate tarball from packages/ directory.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
I, Peter Wielander <mittgfu@gmail.com>, hereby add my Signed-off-by to this commit: c411180

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Jan 23, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.33 ⏵ 0.0.0-alpha.3498 +1100100 +198 +3100

View full report

Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

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

🔧 Build Fix:

The function parameter at line 130 is incompatible with the CallbackHandlers type. The default property returns Promise<void | { timeoutSeconds: number; }> but the handler must return only void | Promise<void>.

Fix on Vercel

Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

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

Additional Suggestion:

Type mismatch between message handler callback return type and @vercel/queue v3 API's MessageHandler type causes TypeScript compilation error

Fix on Vercel

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>

Use delaySeconds for sleep

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Comment thread packages/world/src/queue.ts Outdated
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

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

🔧 Build Fix:

The TypeScript code uses delaySeconds property on QueueOptions type, but this property is not defined in the QueueOptions interface. This causes TypeScript compilation to fail.

Fix on Vercel

Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

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

🔧 Build Fix:

The property delaySeconds does not exist on the QueueOptions type. The code is trying to access and use a property that is not defined in the type definition.

Fix on Vercel

Comment thread packages/world-vercel/src/queue.ts
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Copy link
Copy Markdown
Contributor

@pranaygp pranaygp left a comment

Choose a reason for hiding this comment

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

would love @TooTallNate to approve since he might have had plans for the sleep impl

Comment thread packages/world-vercel/src/queue.ts Outdated
basePath: usingProxy ? '/queues/v3/topic' : undefined,
token: usingProxy ? config?.token : undefined,
headers: Object.fromEntries(headers.entries()),
deploymentId: process.env.VERCEL_DEPLOYMENT_ID,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this needs to be overrideable by options (so that resumeHook can enqueue messages against a different deployment). the same way queue accepts an option to override this

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Fixed

const queue: QueueFunction = async (
queueName,
payload,
opts?: QueueOptions & { delaySeconds?: number }
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

can we just add delaySeconds to QueueOptions? every world supports it no? i think vqs was just the last

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I don't think postgres does? Either way can add separately - it'll be nice to land this directly to bugbash together with event sourcing

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.

4 participants