Skip to content

Submit request bodies with CBOR encoding#844

Merged
TooTallNate merged 4 commits into
mainfrom
01-23-submit_request_bodies_with_cbor_encoding
Jan 27, 2026
Merged

Submit request bodies with CBOR encoding#844
TooTallNate merged 4 commits into
mainfrom
01-23-submit_request_bodies_with_cbor_encoding

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate commented Jan 23, 2026

Updated request body encoding to use CBOR instead of JSON for all API requests in the @workflow/world-vercel package.

What changed?

  • Replaced JSON.stringify with CBOR encoding for all request bodies in the Vercel World package
  • Removed the dateToStringReplacer function as it's no longer needed with CBOR encoding
  • Updated the makeRequest utility to handle CBOR encoding of request bodies
  • Renamed data parameters to requestData to avoid confusion with the data parameter in makeRequest

Why make this change?

CBOR encoding provides several advantages over JSON:

  • More efficient binary encoding, resulting in smaller request payloads
  • Native support for Date objects without needing custom replacers
  • Consistent with the existing response handling which already uses CBOR
  • Improves performance for API requests with large payloads

This change maintains API compatibility while improving the underlying transport mechanism.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jan 23, 2026

🦋 Changeset detected

Latest commit: fdf0013

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

This PR includes changesets to release 16 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/example-nest Patch
@workflow/ai Patch
@workflow/astro Patch
@workflow/nest 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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 23, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 457 0 38 495
❌ 💻 Local Development 416 2 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
✅ 📋 Other 123 0 12 135
Total 1908 163 146 2217

❌ Failed Tests

💻 Local Development (2 failed)

astro-stable (2 failed):

  • 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
🌍 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 39 2 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
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 41 0 4
✅ e2e-local-postgres-nest-stable 41 0 4
✅ e2e-local-prod-nest-stable 41 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.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Jan 23, 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 Jan 26, 2026 11:03pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Jan 26, 2026 11:03pm
example-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-astro-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-express-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-fastify-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-hono-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-nitro-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-nuxt-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workbench-vite-workflow Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workflow-docs Ready Ready Preview, Comment Jan 26, 2026 11:03pm
workflow-nest Error Error Jan 26, 2026 11:03pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 23, 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 🥇 Nitro 0.042s (+1.2%) 1.007s (~) 0.965s 10 1.00x
💻 Local Express 0.043s (+23.2% 🔺) 1.007s (~) 0.964s 10 1.03x
💻 Local Next.js (Turbopack) 0.044s (+9.7% 🔺) 1.019s (~) 0.975s 10 1.04x
🐘 Postgres Nitro 0.257s (+40.3% 🔺) 1.013s (~) 0.756s 10 6.07x
🐘 Postgres Next.js (Turbopack) 0.266s (-25.1% 🟢) 1.020s (~) 0.754s 10 6.28x
🐘 Postgres Express 0.323s (+3.6%) 1.021s (+0.5%) 0.698s 10 7.63x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.662s (-1.6%) 1.607s (-3.8%) 0.946s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.684s (-10.1% 🟢) 1.712s (-2.6%) 1.028s 10 1.03x
▲ Vercel Express 0.774s (-4.0%) 1.800s (+3.4%) 1.027s 10 1.17x

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

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.923s 10 1.00x
💻 Local Express 1.114s (+2.0%) 2.007s (~) 0.894s 10 1.02x
💻 Local Nitro 1.114s (~) 2.006s (~) 0.892s 10 1.02x
🐘 Postgres Next.js (Turbopack) 1.546s (-28.1% 🟢) 2.015s (-20.7% 🟢) 0.470s 10 1.42x
🐘 Postgres Express 2.139s (~) 2.772s (-8.2% 🟢) 0.633s 10 1.96x
🐘 Postgres Nitro 2.203s (-9.2% 🟢) 3.016s (~) 0.813s 10 2.02x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.861s (+2.7%) 3.728s (-0.5%) 0.867s 10 1.00x
▲ Vercel Express 2.914s (-1.0%) 3.841s (+2.0%) 0.927s 10 1.02x
▲ Vercel Next.js (Turbopack) 3.041s (+7.3% 🔺) 3.798s (+0.6%) 0.757s 10 1.06x

🔍 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.708s (~) 11.020s (~) 0.312s 5 1.00x
💻 Local Nitro 10.820s (~) 11.014s (~) 0.194s 5 1.01x
💻 Local Express 10.831s (+1.8%) 11.015s (~) 0.185s 5 1.01x
🐘 Postgres Next.js (Turbopack) 14.615s (-7.5% 🟢) 14.833s (-8.7% 🟢) 0.218s 5 1.36x
🐘 Postgres Express 16.742s (-18.3% 🟢) 17.437s (-17.1% 🟢) 0.695s 5 1.56x
🐘 Postgres Nitro 20.455s (+1.0%) 21.031s (~) 0.576s 5 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 22.694s (-1.0%) 23.422s (~) 0.728s 5 1.00x
▲ Vercel Nitro 22.866s (~) 23.484s (~) 0.618s 5 1.01x
▲ Vercel Express 23.154s (+1.0%) 24.138s (+1.8%) 0.984s 5 1.02x

🔍 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.392s (~) 2.006s (~) 0.615s 15 1.00x
💻 Local Next.js (Turbopack) 1.415s (+3.0%) 2.011s (~) 0.596s 15 1.02x
💻 Local Nitro 1.421s (+0.9%) 2.007s (~) 0.586s 15 1.02x
🐘 Postgres Next.js (Turbopack) 2.122s (+13.7% 🔺) 2.519s (+7.2% 🔺) 0.397s 12 1.52x
🐘 Postgres Nitro 2.195s (-11.5% 🟢) 3.013s (~) 0.818s 10 1.58x
🐘 Postgres Express 2.299s (+1.6%) 2.975s (-1.3%) 0.676s 11 1.65x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.237s (-11.5% 🟢) 3.945s (-14.5% 🟢) 0.708s 8 1.00x
▲ Vercel Nitro 3.295s (+4.3%) 3.964s (-4.0%) 0.668s 8 1.02x
▲ Vercel Next.js (Turbopack) 3.420s (+11.9% 🔺) 4.180s (+8.3% 🔺) 0.760s 8 1.06x

🔍 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 🥇 Nitro 2.494s (+1.7%) 3.032s (~) 0.538s 10 1.00x
💻 Local Express 2.500s (+6.7% 🔺) 3.016s (-8.9% 🟢) 0.516s 10 1.00x
💻 Local Next.js (Turbopack) 2.509s (+3.5%) 3.039s (-7.0% 🟢) 0.530s 10 1.01x
🐘 Postgres Nitro 9.384s (+3.6%) 10.058s (+5.6% 🔺) 0.674s 3 3.76x
🐘 Postgres Express 9.463s (+14.7% 🔺) 9.901s (+9.4% 🔺) 0.438s 4 3.79x
🐘 Postgres Next.js (Turbopack) 13.223s (+36.5% 🔺) 14.052s (+37.8% 🔺) 0.829s 3 5.30x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.253s (-2.7%) 3.861s (-6.5% 🟢) 0.608s 8 1.00x
▲ Vercel Express 3.275s (~) 3.790s (-5.4% 🟢) 0.515s 8 1.01x
▲ Vercel Next.js (Turbopack) 3.602s (+9.0% 🔺) 4.136s (+3.6%) 0.534s 8 1.11x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.406s (-1.3%) 2.011s (~) 0.604s 15 1.00x
💻 Local Express 1.421s (~) 2.007s (~) 0.586s 15 1.01x
💻 Local Nitro 1.441s (+1.9%) 2.006s (~) 0.566s 15 1.02x
🐘 Postgres Express 2.005s (-5.3% 🟢) 2.522s (~) 0.517s 13 1.43x
🐘 Postgres Nitro 2.059s (-1.9%) 2.604s (-5.6% 🟢) 0.545s 12 1.46x
🐘 Postgres Next.js (Turbopack) 2.266s (+26.7% 🔺) 2.742s (+29.0% 🔺) 0.477s 11 1.61x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.854s (-3.3%) 3.703s (-3.7%) 0.849s 9 1.00x
▲ Vercel Express 2.978s (+2.8%) 3.936s (+4.4%) 0.958s 8 1.04x
▲ Vercel Next.js (Turbopack) 3.064s (+5.6% 🔺) 3.996s (+8.4% 🔺) 0.932s 8 1.07x

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

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.542s (+3.5%) 3.042s (~) 0.501s 10 1.00x
💻 Local Express 2.555s (+1.1%) 3.020s (-13.0% 🟢) 0.466s 10 1.01x
💻 Local Nitro 2.622s (+3.5%) 3.025s (+0.5%) 0.403s 10 1.03x
🐘 Postgres Express 8.105s (-33.6% 🟢) 8.723s (-29.4% 🟢) 0.617s 4 3.19x
🐘 Postgres Nitro 11.857s (+0.8%) 12.384s (+2.1%) 0.528s 3 4.66x
🐘 Postgres Next.js (Turbopack) 13.244s (+17.4% 🔺) 13.710s (+16.4% 🔺) 0.466s 3 5.21x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.105s (-16.6% 🟢) 3.839s (-19.1% 🟢) 0.734s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.270s (+0.7%) 3.908s (-3.6%) 0.638s 8 1.05x
▲ Vercel Nitro 4.009s (+31.2% 🔺) 4.593s (+19.6% 🔺) 0.584s 7 1.29x

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

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.146s (+4.8%) 1.004s (~) 0.016s (+1.3%) 1.028s (~) 0.882s 10 1.00x
💻 Local Express 0.182s (+39.6% 🔺) 0.992s (-0.8%) 0.015s (+24.4% 🔺) 1.021s (~) 0.839s 10 1.24x
💻 Local Nitro 0.183s (+2.8%) 0.992s (~) 0.014s (+5.1% 🔺) 1.021s (~) 0.837s 10 1.25x
🐘 Postgres Next.js (Turbopack) 0.786s (-42.1% 🟢) 0.836s (-54.4% 🟢) 0.000s (-100.0% 🟢) 1.017s (-50.1% 🟢) 0.231s 10 5.37x
🐘 Postgres Express 1.752s (-24.3% 🟢) 1.817s (-33.4% 🟢) 0.000s (-100.0% 🟢) 2.150s (-28.7% 🟢) 0.399s 10 11.97x
🐘 Postgres Nitro 2.258s (+0.6%) 2.784s (~) 0.000s (NaN%) 3.016s (~) 0.758s 10 15.42x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.019s (+2.0%) 3.228s (~) 0.540s (+33.6% 🔺) 4.367s (+4.7%) 1.349s 10 1.00x
▲ Vercel Next.js (Turbopack) 3.062s (+1.5%) 3.216s (-0.8%) 0.478s (-6.4% 🟢) 4.229s (-0.7%) 1.166s 10 1.01x
▲ Vercel Nitro 3.179s (+13.7% 🔺) 3.433s (+4.2%) 0.475s (+40.6% 🔺) 4.428s (+7.4% 🔺) 1.249s 10 1.05x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 5/8
🐘 Postgres Next.js (Turbopack) 4/8
▲ Vercel Nitro 4/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

Copy link
Copy Markdown
Member Author

TooTallNate commented Jan 23, 2026

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 switches the @workflow/world-vercel client from JSON to CBOR for all request bodies, aligning request encoding with the existing CBOR-based response handling. It also refactors the shared makeRequest utility to own body construction and simplifies call sites to pass typed data instead of pre-encoded payloads.

Changes:

  • Add CBOR encoding for request bodies via cbor-x.encode in makeRequest, and update headers to prefer application/cbor.
  • Update runs, steps, hooks, and events APIs to pass high-level data objects (including serializeError outputs) into makeRequest instead of JSON strings.
  • Remove the now-unnecessary dateToStringReplacer helper and adjust imports accordingly, plus add a changeset entry for @workflow/world-vercel.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
packages/world-vercel/src/utils.ts Adds CBOR request-body encoding in makeRequest, adjusts accepted/Content-Type headers, and (currently) overrides the workflow-server base URL to a specific preview deployment.
packages/world-vercel/src/steps.ts Updates step creation and update calls to use makeRequest’s data parameter with CBOR, and uses serializeError for step error payloads.
packages/world-vercel/src/runs.ts Switches workflow run create/update calls to pass structured data into makeRequest (including serializeError), relying on CBOR encoding.
packages/world-vercel/src/hooks.ts Updates hook creation to pass a merged { runId, ...data } object as data into makeRequest for CBOR encoding and removes JSON-specific utilities.
packages/world-vercel/src/events.ts Changes workflow-run event creation to send CBOR-encoded data via makeRequest and removes JSON-specific plumbing.
.changeset/eighty-bikes-jog.md Records a patch release note for @workflow/world-vercel describing the CBOR encoding change for request bodies.

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

Comment thread packages/world-vercel/src/utils.ts Outdated
headers.set('X-Request-Time', Date.now().toString());

// Encode body as CBOR if data is provided
let body: Buffer | undefined;
Copy link

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

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

body is typed as Buffer | undefined, but encode from cbor-x returns a Uint8Array, which is not assignable to Buffer in TypeScript and also unnecessarily couples this helper to Node-specific types. To avoid type errors and keep this utility usable in edge/runtime environments, consider typing body as a BodyInit | null (or at least Uint8Array | undefined) and letting the Fetch implementation accept the binary payload directly.

Suggested change
let body: Buffer | undefined;
let body: BodyInit | null | undefined;

Copilot uses AI. Check for mistakes.
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 OpenAI class from the openai package cannot be constructed because the type definition has no construct signatures. This indicates the imported type is not a constructor or the OpenAI export format has changed.

Fix on Vercel

@TooTallNate TooTallNate merged commit b59559b into main Jan 27, 2026
150 of 154 checks passed
@TooTallNate TooTallNate deleted the 01-23-submit_request_bodies_with_cbor_encoding branch January 27, 2026 00:56
pranaygp added a commit that referenced this pull request Jan 28, 2026
…s-and-commands

* origin/main:
  fix(@workflow/ai): support provider-executed tools (AI SDK v6) (#734)
  Publish "workflow" and "@workflow/core" package versions in sync (#870)
  Add SDK version to workflow run executionContext for observability (#868)
  Allow recreateRun to accept an optional deploymentId parameter (#869)
  Add support for top-level `using` declarations inside of step / workflow functions (#866)
  docs: URL in docs was missing the docs/ prefix, 404 errors (#852)
  Add "classes" object to `manifest.json` file (#864)
  Fix Nest workbench app build (#865)
  Ignore Astro on local dev tests for source map e2e tests (#863)
  Enable custom class serialization transformations for "client" mode (#860)
  Submit request bodies with CBOR encoding (#844)
  [world-vercel] Update queue to use VQS v3 API (#799)
  NestJS framework support (#840)
  Fix resolve hook theming and token fetching. (#856)
  docs: rename Control Flow Patterns to Common Patterns and add new content (#846)
  docs: revamp World documentation pages (#763)
  Remove unused `getWritable` stub function (#855)

# Conflicts:
#	packages/core/package.json
#	pnpm-lock.yaml
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.

3 participants