New and improved manifest.json format

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.

[TooTallNate]

Overview

The manifest.json format has been inverted from a file-path-keyed structure to an ID-keyed structure. This makes it easier to look up entries by their ID and allows manifest entries to be passed directly to APIs like start().

Old Format (file-path-keyed)

{
steps: {
workflows/addition.ts: {
add: {
stepId: step//./workflows/addition//add
}
}
},
workflows: {
workflows/addition.ts: {
addition: {
workflowId: workflow//./workflows/addition//addition
}
}
}
}

New Format (ID-keyed)

{
steps: {
step//./workflows/addition//add: {
stepId: step//./workflows/addition//add,
name: add,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
}
}
},
workflows: {
workflow//./workflows/addition//addition: {
workflowId: workflow//./workflows/addition//addition,
name: addition,
exports: {
default: workflows/addition.ts,
workflow: workflows/addition.ts
},
graph: {
nodes: [],
edges: []
}
}
},
classes: {
class//./utils/point//Point: {
classId: class//./utils/point//Point,
name: Point,
exports: {
default: utils/point.ts,
workflow: utils/point.ts
}
}
}
}

Key Changes

Aspect	Old Format	New Format
Primary key	File path	Full ID (e.g., step//./path//name)
Secondary key	Function/class name	N/A (flat structure)
ID field	Only field in entry	Included alongside other fields
Name field	Used as key	Explicit name field
Source/exports	Not included	exports object with condition keys

Benefits

1. Direct API usage: Manifest entries can be passed directly to start() since they include workflowId
2. O(1) lookups: Find any entry by ID without iterating through file paths
3. Export conditions: The exports object maps bundle conditions (default, workflow) to source files
4. Self-describing: Each entry contains its own ID, making entries portable and self-contained

Migration Notes

Code that previously accessed the manifest like this:

// Old formatconstworkflow=manifest.workflows[filePath][functionName];constid=workflow.workflowId;

Should now use:

// New format - direct lookup by IDconstworkflow=manifest.workflows[workflowId];// Or find by nameconstworkflow=Object.values(manifest.workflows).find(w=>w.name===functionName);

[changeset-bot]

🦋 Changeset detected

Latest commit: e5b5cff

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/world-testing	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nest	Patch
@workflow/next	Patch
workflow-devkit-compiler-playground	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/web-shared	Patch

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

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

redis (42 failed):

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

starter (43 failed):

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

turso (42 failed):

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

Details by Category

✅ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro	43	0	4
✅ example	43	0	4
✅ express	43	0	4
✅ fastify	43	0	4
✅ hono	43	0	4
✅ nextjs-turbopack	46	0	1
✅ nextjs-webpack	46	0	1
✅ nitro	43	0	4
✅ nuxt	43	0	4
✅ sveltekit	43	0	4
✅ vite	43	0	4

✅ 💻 Local Development

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 📦 Local Production

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🐘 Local Postgres

App	Passed	Failed	Skipped
✅ astro-stable	43	0	4
✅ express-stable	43	0	4
✅ fastify-stable	43	0	4
✅ hono-stable	43	0	4
✅ nextjs-turbopack-stable	47	0	0
✅ nextjs-webpack-stable	47	0	0
✅ nitro-stable	43	0	4
✅ nuxt-stable	43	0	4
✅ sveltekit-stable	43	0	4
✅ vite-stable	43	0	4

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack	47	0	0

❌ 🌍 Community Worlds

App	Passed	Failed	Skipped
✅ mongodb-dev	3	0	0
❌ mongodb	5	42	0
✅ redis-dev	3	0	0
❌ redis	5	42	0
✅ starter-dev	3	0	0
❌ starter	4	43	0
✅ turso-dev	3	0	0
❌ turso	5	42	0

✅ 📋 Other

App	Passed	Failed	Skipped
✅ e2e-local-dev-nest-stable	43	0	4
✅ e2e-local-postgres-nest-stable	43	0	4
✅ e2e-local-prod-nest-stable	43	0	4

---

📋 View full workflow run

[vercel]

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

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

[TooTallNate]

• New and improved manifest.json format #902 👈 (View in Graphite)
• Add subpath export resolution for package IDs #901
• Change compiler ID generation logic to use Node.js import specifier #899
• Add support for "use step" functions in class instance methods #777: 1 other dependent PR (#876)
• Add discovered serializable classes in all context modes #874
• Ensure class serialization / deserialization only happens in the proper global context #873
• Fix class ID generation when class is bound to a variable #872
• Add discovery for custom classes with workflow serialization #859
• main

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

[Copilot]

Pull request overview

This PR refactors the manifest.json format from a file-path-keyed structure to an ID-keyed structure, making manifest entries directly usable with APIs like start() and enabling O(1) lookups by ID.

Changes:

• Rust SWC plugin now emits ID-keyed manifest format with name and source fields
• TypeScript builders convert raw manifests (with source) to final manifests (with exports keyed by condition)
• New mergeManifests utility provides deep merging of exports from multiple bundle contexts
• All test fixtures, integration tests, and documentation updated to reflect the new format

Reviewed changes

Copilot reviewed 148 out of 148 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/swc-plugin-workflow/transform/src/lib.rs	Rust transform updated to emit ID-keyed format with name/source fields
packages/builders/src/apply-swc-transform.ts	Added RawWorkflowManifest and updated WorkflowManifest types for new format
packages/builders/src/manifest-utils.ts	New file with deepMergeManifestEntries and mergeManifests utilities
packages/builders/src/base-builder.ts	Updated mergeRawManifest and addGraphsToWorkflows for new format
packages/builders/src/swc-esbuild-plugin.ts	Added mergeRawManifest function to convert raw to final manifest
packages/sveltekit/src/builder.ts	Updated to use new mergeManifests utility
packages/nitro/src/builders.ts	Updated to use new mergeManifests utility
packages/next/src/builder.ts	Updated to use new mergeManifests utility
packages/nest/src/builder.ts	Updated to use new mergeManifests utility
packages/builders/src/standalone.ts	Removed local mergeManifests in favor of shared utility
packages/builders/src/vercel-build-output-api.ts	Updated to use new mergeManifests utility
packages/builders/src/index.ts	Exported new mergeManifests utilities
packages/core/e2e/manifest.test.ts	Updated tests for ID-keyed manifest structure
workbench/example/api/trigger.ts	Updated to look up workflows by ID with backwards compatibility
packages/world-testing/src/*.mts	Updated to use ID-keyed manifest for workflow invocation
packages/swc-plugin-workflow/spec.md	Comprehensive documentation update explaining new format
All test fixture files	Updated expected output for new manifest format

---

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

[pranaygp]

Code Review Summary

The core changes are solid and well-implemented. The transformation from file-path-keyed to ID-keyed manifest format is correctly implemented across all packages with good test coverage and excellent documentation.

Highlights

• Well-documented PR description with clear migration notes
• New manifest-utils.ts provides clean, reusable utilities
• Types are well-defined with RawWorkflowManifest vs WorkflowManifest distinction
• SWC plugin spec document updated comprehensively
• O(1) lookups by ID is a nice performance improvement

Minor Suggestions (non-blocking)

1. Duplicate mergeRawManifest function - The function exists in both base-builder.ts:27-48 and swc-esbuild-plugin.ts:26-51. Consider consolidating into manifest-utils.ts.

2. Use of any types in manifest-utils.ts:20-23 - Could use proper typing given WorkflowManifest types are available:

   typeManifestEntry={name: string;exports: Record<string,string>;[key: string]: unknown;};

3. Consider marking as breaking in changeset if this affects external tooling that reads manifest.json.

4. Graph lookup fallback - In addGraphsToWorkflows, the lookup relies on exports.workflow being present. Consider checking both exports.workflow and exports.default.

LGTM! 🚀

[pranaygp]

This is a significant format change. Should this be marked as BREAKING CHANGE per project conventions if external tooling reads manifest.json?

[TooTallNate]

This is a valid concern. However, the manifest.json format is currently internal to the build tooling and not intended as a public API for external consumers. The format is read by our own runtime and tooling. If there are external tools relying on this format, we should document and version it properly in a separate PR. For now, keeping this as a patch release seems appropriate since it's an internal improvement.

[VaguelySerious]

web-shared and web o11y code use the manifest and should presumably be updated, CC @karthikscale3

[github-actions]

📊 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.039s (+2.9%)	1.017s (~)	0.978s	10	1.00x
💻 Local	Nitro	0.042s (+48.3% 🔺)	1.008s (~)	0.966s	10	1.08x
💻 Local	Express	0.043s (-2.3%)	1.007s (~)	0.964s	10	1.10x
🐘 Postgres	Nitro	0.199s (-41.9% 🟢)	1.014s (~)	0.815s	10	5.09x
🐘 Postgres	Express	0.270s (+14.2% 🔺)	1.014s (~)	0.745s	10	6.89x
🐘 Postgres	Next.js (Turbopack)	0.362s (+7.5% 🔺)	1.022s (-1.2%)	0.660s	10	9.23x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	0.582s (-11.2% 🟢)	1.639s (+10.4% 🔺)	1.057s	10	1.00x
▲ Vercel	Nitro	0.678s (-7.5% 🟢)	1.484s (-14.9% 🟢)	0.806s	10	1.16x
▲ Vercel	Next.js (Turbopack)	0.678s (-1.0%)	1.484s (-3.2%)	0.806s	10	1.17x

🔍 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.105s (+0.9%)	2.013s (~)	0.908s	10	1.00x
💻 Local	Nitro	1.115s (+3.3%)	2.007s (~)	0.892s	10	1.01x
💻 Local	Express	1.116s (~)	2.007s (~)	0.891s	10	1.01x
🐘 Postgres	Express	2.154s (-3.2%)	3.017s (~)	0.863s	10	1.95x
🐘 Postgres	Next.js (Turbopack)	2.212s (+8.0% 🔺)	2.921s (+3.5%)	0.709s	10	2.00x
🐘 Postgres	Nitro	2.330s (-1.9%)	3.015s (~)	0.685s	10	2.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.767s (-4.1%)	3.736s (+2.0%)	0.969s	10	1.00x
▲ Vercel	Nitro	2.773s (-11.0% 🟢)	3.702s (-6.4% 🟢)	0.929s	10	1.00x
▲ Vercel	Next.js (Turbopack)	2.779s (-4.0%)	3.661s (~)	0.882s	10	1.00x

🔍 Observability: Express | Nitro | 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.728s (~)	11.021s (~)	0.293s	3	1.00x
💻 Local	Express	10.842s (~)	11.017s (~)	0.175s	3	1.01x
💻 Local	Nitro	10.859s (+2.8%)	11.017s (~)	0.158s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	15.098s (~)	16.041s (+3.3%)	0.943s	2	1.41x
🐘 Postgres	Nitro	15.671s (-22.6% 🟢)	16.033s (-23.8% 🟢)	0.362s	2	1.46x
🐘 Postgres	Express	20.512s (~)	21.034s (~)	0.522s	2	1.91x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	22.356s (-1.5%)	23.602s (+2.3%)	1.246s	2	1.00x
▲ Vercel	Next.js (Turbopack)	22.709s (-3.8%)	23.792s (-0.9%)	1.083s	2	1.02x
▲ Vercel	Nitro	22.985s (-1.5%)	23.324s (-4.0%)	0.340s	2	1.03x

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

workflow with 25 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	27.215s (~)	28.041s (~)	0.826s	3	1.00x
💻 Local	Express	27.485s (~)	28.029s (~)	0.544s	3	1.01x
💻 Local	Nitro	27.564s (+2.9%)	28.034s (+3.7%)	0.470s	3	1.01x
🐘 Postgres	Next.js (Turbopack)	38.023s (+1.8%)	38.547s (+1.2%)	0.523s	2	1.40x
🐘 Postgres	Nitro	39.058s (-21.6% 🟢)	39.560s (-21.8% 🟢)	0.502s	2	1.44x
🐘 Postgres	Express	50.425s (~)	51.073s (~)	0.648s	2	1.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	56.721s (-1.9%)	57.529s (-1.3%)	0.808s	2	1.00x
▲ Vercel	Nitro	57.728s (~)	58.766s (~)	1.038s	2	1.02x
▲ Vercel	Express	58.147s (+1.4%)	58.952s (+1.1%)	0.805s	2	1.03x

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

workflow with 50 sequential steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	56.740s (+0.5%)	57.060s (~)	0.320s	2	1.00x
💻 Local	Express	57.319s (~)	58.046s (~)	0.726s	2	1.01x
💻 Local	Nitro	57.468s (+3.3%)	58.044s (+3.6%)	0.576s	2	1.01x
🐘 Postgres	Next.js (Turbopack)	75.369s (~)	76.129s (~)	0.760s	2	1.33x
🐘 Postgres	Nitro	86.881s (-13.5% 🟢)	87.112s (-13.9% 🟢)	0.231s	2	1.53x
🐘 Postgres	Express	100.233s (~)	101.156s (~)	0.923s	1	1.77x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	117.016s (-1.9%)	117.547s (-2.2%)	0.531s	1	1.00x
▲ Vercel	Nitro	117.662s (-5.7% 🟢)	118.650s (-5.1% 🟢)	0.988s	1	1.01x
▲ Vercel	Next.js (Turbopack)	118.620s (-2.7%)	119.046s (-3.0%)	0.426s	1	1.01x

🔍 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.405s (+2.2%)	2.010s (~)	0.606s	15	1.00x
💻 Local	Express	1.415s (-1.0%)	2.007s (~)	0.592s	15	1.01x
💻 Local	Nitro	1.446s (+6.8% 🔺)	2.007s (~)	0.561s	15	1.03x
🐘 Postgres	Next.js (Turbopack)	2.102s (-10.3% 🟢)	2.751s (+1.7%)	0.648s	11	1.50x
🐘 Postgres	Nitro	2.313s (-7.4% 🟢)	3.013s (~)	0.700s	10	1.65x
🐘 Postgres	Express	2.345s (+4.0%)	3.014s (~)	0.668s	10	1.67x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	2.769s (-14.4% 🟢)	3.616s (-11.7% 🟢)	0.847s	9	1.00x
▲ Vercel	Express	2.914s (+1.0%)	3.944s (+4.2%)	1.030s	8	1.05x
▲ Vercel	Nitro	2.963s (~)	3.842s (-2.2%)	0.879s	8	1.07x

🔍 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	🥇 Next.js (Turbopack)	2.501s (+1.4%)	3.039s (~)	0.537s	10	1.00x
💻 Local	Express	2.605s (-1.6%)	3.013s (~)	0.409s	10	1.04x
💻 Local	Nitro	2.660s (+18.9% 🔺)	3.014s (-6.3% 🟢)	0.354s	10	1.06x
🐘 Postgres	Express	9.178s (+3.9%)	9.856s (+5.9% 🔺)	0.678s	4	3.67x
🐘 Postgres	Nitro	9.321s (+11.0% 🔺)	10.041s (+11.1% 🔺)	0.720s	3	3.73x
🐘 Postgres	Next.js (Turbopack)	12.782s (-5.5% 🟢)	13.371s (-4.7%)	0.589s	3	5.11x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.734s (+3.7%)	4.477s (+4.0%)	0.743s	7	1.00x
▲ Vercel	Nitro	4.184s (+16.0% 🔺)	4.914s (-6.7% 🟢)	0.730s	7	1.12x
▲ Vercel	Express	5.175s (+70.3% 🔺)	5.733s (+50.8% 🔺)	0.557s	6	1.39x

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

Promise.all with 50 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	6.901s (+6.6% 🔺)	7.575s (+5.8% 🔺)	0.674s	5	1.00x
💻 Local	Express	7.444s (-4.7%)	8.435s (-3.3%)	0.991s	4	1.08x
💻 Local	Nitro	7.689s (+25.7% 🔺)	8.676s (+28.7% 🔺)	0.987s	4	1.11x
🐘 Postgres	Nitro	47.695s (-6.8% 🟢)	48.189s (-7.6% 🟢)	0.494s	1	6.91x
🐘 Postgres	Express	51.132s (+7.1% 🔺)	51.462s (+6.5% 🔺)	0.330s	1	7.41x
🐘 Postgres	Next.js (Turbopack)	52.865s (-4.8%)	53.101s (-5.7% 🟢)	0.236s	1	7.66x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.512s (-5.9% 🟢)	4.038s (-9.4% 🟢)	0.526s	8	1.00x
▲ Vercel	Nitro	3.661s (+4.8%)	4.344s (+5.4% 🔺)	0.682s	8	1.04x
▲ Vercel	Express	3.792s (+9.8% 🔺)	4.407s (+7.7% 🔺)	0.615s	7	1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
💻 Local	🥇 Next.js (Turbopack)	1.434s (+1.6%)	2.011s (~)	0.577s	15	1.00x
💻 Local	Express	1.446s (~)	2.006s (~)	0.560s	15	1.01x
💻 Local	Nitro	1.469s (+8.2% 🔺)	2.007s (~)	0.538s	15	1.02x
🐘 Postgres	Express	2.084s (+3.8%)	2.515s (-3.7%)	0.431s	12	1.45x
🐘 Postgres	Next.js (Turbopack)	2.120s (-5.2% 🟢)	2.606s (-8.3% 🟢)	0.486s	12	1.48x
🐘 Postgres	Nitro	2.237s (+6.0% 🔺)	2.833s (+12.1% 🔺)	0.597s	11	1.56x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Express	2.672s (-8.1% 🟢)	3.774s (+2.4%)	1.102s	8	1.00x
▲ Vercel	Nitro	2.786s (-1.6%)	3.633s (-2.7%)	0.847s	9	1.04x
▲ Vercel	Next.js (Turbopack)	2.810s (-0.8%)	3.660s (~)	0.849s	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	🥇 Express	2.676s (-7.3% 🟢)	3.015s (-0.7%)	0.338s	10	1.00x
💻 Local	Next.js (Turbopack)	2.718s (+3.3%)	3.021s (~)	0.303s	10	1.02x
💻 Local	Nitro	2.727s (+16.7% 🔺)	3.034s (-8.3% 🟢)	0.307s	10	1.02x
🐘 Postgres	Express	10.088s (-16.4% 🟢)	10.703s (-13.5% 🟢)	0.616s	3	3.77x
🐘 Postgres	Nitro	12.878s (+5.5% 🔺)	13.083s (+5.9% 🔺)	0.205s	3	4.81x
🐘 Postgres	Next.js (Turbopack)	12.974s (-3.3%)	13.375s (-3.0%)	0.401s	3	4.85x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.946s (-1.1%)	3.811s (+2.0%)	0.864s	8	1.00x
▲ Vercel	Next.js (Turbopack)	3.105s (+4.5%)	3.776s (-1.0%)	0.672s	8	1.05x
▲ Vercel	Express	3.108s (+2.4%)	3.986s (+9.6% 🔺)	0.878s	8	1.05x

🔍 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.594s (+11.0% 🔺)	8.132s (-1.2%)	0.538s	4	1.00x
💻 Local	Express	7.981s (-1.6%)	8.789s (+3.9%)	0.808s	4	1.05x
💻 Local	Nitro	8.275s (+26.8% 🔺)	9.235s (+22.6% 🔺)	0.959s	4	1.09x
🐘 Postgres	Express	50.392s (-3.5%)	51.147s (-3.9%)	0.755s	1	6.64x
🐘 Postgres	Nitro	52.298s (-2.0%)	53.129s (-1.9%)	0.831s	1	6.89x
🐘 Postgres	Next.js (Turbopack)	56.811s (+1.2%)	57.197s (+1.6%)	0.386s	1	7.48x

▲ Production (Vercel)

World	Framework	Workflow Time	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Next.js (Turbopack)	3.376s (+1.5%)	3.943s (~)	0.567s	8	1.00x
▲ Vercel	Express	3.505s (-10.7% 🟢)	4.302s (-4.3%)	0.797s	7	1.04x
▲ Vercel	Nitro	4.008s (+26.2% 🔺)	4.533s (+19.7% 🔺)	0.525s	7	1.19x

🔍 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	🥇 Next.js (Turbopack)	0.148s (+4.5%)	1.003s (~)	0.015s (+2.7%)	1.027s (~)	0.879s	10	1.00x
💻 Local	Express	0.184s (-2.9%)	0.992s (~)	0.015s (-0.7%)	1.022s (~)	0.838s	10	1.24x
💻 Local	Nitro	0.186s (+60.9% 🔺)	0.993s (-0.7%)	0.014s (+22.4% 🔺)	1.022s (~)	0.836s	10	1.26x
🐘 Postgres	Next.js (Turbopack)	1.021s (-14.3% 🟢)	1.452s (-21.7% 🟢)	0.001s (+Infinity% 🔺)	1.621s (-19.7% 🟢)	0.600s	10	6.91x
🐘 Postgres	Nitro	1.333s (+16.3% 🔺)	1.705s (-10.0% 🟢)	0.000s (-100.0% 🟢)	2.013s (~)	0.680s	10	9.03x
🐘 Postgres	Express	2.426s (+2.0%)	2.618s (-1.8%)	0.000s (~)	3.015s (~)	0.590s	10	16.42x

▲ Production (Vercel)

World	Framework	Workflow Time	TTFB	Slurp	Wall Time	Overhead	Samples	vs Fastest
▲ Vercel	🥇 Nitro	2.895s (+1.5%)	3.279s (~)	0.246s (+9.0% 🔺)	4.031s (+1.4%)	1.136s	10	1.00x
▲ Vercel	Next.js (Turbopack)	3.028s (+1.1%)	3.181s (-3.8%)	0.226s (+29.6% 🔺)	3.933s (-1.2%)	0.904s	10	1.05x
▲ Vercel	Express	3.120s (+4.0%)	3.393s (+1.9%)	0.247s (+53.7% 🔺)	4.204s (+6.0% 🔺)	1.084s	10	1.08x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World	🥇 Fastest Framework	Wins
💻 Local	Next.js (Turbopack)	11/12
🐘 Postgres	Express	5/12
▲ Vercel	Express	5/12

Fastest World by Framework

Winner determined by most benchmark wins

Framework	🥇 Fastest World	Wins
Express	💻 Local	10/12
Next.js (Turbopack)	💻 Local	10/12
Nitro	💻 Local	10/12

Column Definitions

• Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
• TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
• Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
• Wall Time: Total testbench time (trigger workflow + poll for result)
• Overhead: Testbench overhead (Wall Time - Workflow Time)
• Samples: Number of benchmark iterations run
• vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

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

---

📋 View full workflow run

[TooTallNate]

Addressed the backwards compatibility concern for web-shared and web o11y tooling.

The manifest-adapter.ts in the web package now detects and handles both formats:

• Legacy (pre-1.0.0): file-path keyed structure { [filePath]: { [workflowName]: { workflowId, graph } } }
• New (1.0.0+): ID-keyed structure { [workflowId]: { name, exports, graph } }

The adapter auto-detects the format by checking for the presence of name and exports fields in workflow entries. This ensures the web UI can display workflow graphs from both old and new deployments during the transition period.

See commit e5b5cff for the changes.