Fix module specifier cache bug and add subpath export resolution for package IDs

[TooTallNate]

TL;DR

Fixed a bug in module specifier resolution and added support for package subpath exports in workflow IDs.

What changed?

• Fixed a caching bug in the module specifier resolution system that could cause incorrect IDs
• Added support for subpath exports in package IDs (e.g., workflow/internal/[email protected])
• Improved module resolution by passing absolute file paths to the SWC transform
• Enhanced manifest merging to properly combine results from both workflow and step bundles
• Updated builders to return and merge manifests from both workflow and step bundles

How to test?

1. Build a project that uses subpath exports in packages
2. Verify that workflow IDs correctly include the subpath (e.g., workflow/internal/[email protected])
3. Test with a project that has multiple builds to ensure module specifier caching works correctly

Why make this change?

This change addresses an issue where the module specifier cache could return incorrect results, leading to inconsistent workflow IDs. It also adds support for packages with multiple entry points through subpath exports, ensuring that steps with the same name in different subpaths don't collide. This improves the reliability of cross-bundle references and makes the system more robust when working with complex package structures.

[changeset-bot]

🦋 Changeset detected

Latest commit: af6cbdc

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

This PR includes changesets to release 16 packages

Name	Type
@workflow/swc-plugin	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/nitro	Patch
@workflow/nest	Patch
@workflow/next	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/rollup	Patch
workflow	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch
@workflow/docs-typecheck	Patch
@workflow/world-testing	Patch
@workflow/core	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

[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 3, 2026 8:14am
example-nextjs-workflow-webpack	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
example-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-astro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-express-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-fastify-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-hono-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-nitro-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-nuxt-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-sveltekit-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workbench-vite-workflow	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workflow-docs	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am
workflow-nest	Ready	Preview, Comment, Open in v0	Feb 3, 2026 8:14am

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

Summary

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

❌ Failed Tests

▲ Vercel Production (11 failed)

express (1 failed):

• error handling retry behavior regular Error retries until success

nextjs-turbopack (2 failed):

• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• error handling retry behavior regular Error retries until success

nextjs-webpack (2 failed):

• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• error handling retry behavior regular Error retries until success

nitro (2 failed):

• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• error handling retry behavior regular Error retries until success

sveltekit (2 failed):

• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• error handling retry behavior regular Error retries until success

vite (2 failed):

• outputStreamInsideStepWorkflow - getWritable() called inside step functions
• error handling retry behavior regular Error retries until success

🪟 Windows (1 failed)

nextjs-turbopack (1 failed):

• fetchWorkflow

🌍 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	42	1	4
✅ fastify	43	0	4
✅ hono	43	0	4
❌ nextjs-turbopack	44	2	1
❌ nextjs-webpack	44	2	1
❌ nitro	41	2	4
✅ nuxt	43	0	4
❌ sveltekit	41	2	4
❌ vite	41	2	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	46	1	0

❌ 🌍 Community Worlds

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

✅ 📋 Other

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

---

📋 View full workflow run

---

❌ Some E2E test jobs failed:

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

Check the workflow run for details.

[TooTallNate]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Fix discovery of serde classes to detect [WORKFLOW_SERIALIZE] and [WORKFLOW_DESERIALIZE] computed property usage in bundled code #908
• New and improved manifest.json format #902
• Fix module specifier cache bug and add subpath export resolution for package IDs #901 👈 (View in Graphite)
• 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.