[nitro] Fix Nitro v2 dev builds against installed workflow packages by VaguelySerious · Pull Request #4551 · vercel/workflow

VaguelySerious · 2026-10-01T01:37:15Z

nuxt dev fails on 5.0.0 whenever the workflow packages come from npm. The first symptom is a dev build error:

[nitro] RollupError: "./run.js" is imported as an external by
"node_modules/.pnpm/@workflow+core@5.0.0/node_modules/@workflow/core/dist/runtime/lifecycle-hooks.js",
but is already an existing non-external module id.

Production builds aren't affected, and neither is the monorepo, because workspace packages resolve outside node_modules and Nitro never externalizes them. That's why CI's nuxt dev lanes pass. Fixing the build error exposes two more failures, and all three are fixed here:

workflow:force-inline misses relative imports (@workflow/nitro). In dev it inlines workflow packages by specifier (@workflow/core/runtime/run), but lifecycle-hooks.js imports the same file as ./run.js. nitro:externals externalizes that path because it's under node_modules, and Rollup aborts. The plugin now also inlines relative imports whose importer is inside an installed workflow package.
World registration is tree-shaken (@workflow/nitro). nitropack 2 treats every module as side-effect free unless it's listed in moduleSideEffects. Once @workflow/core is bundled, the world-init side-effect import is dropped, and every start() throws Workflow world runtime was not initialized. The module now adds @workflow/ and workflow/ to moduleSideEffects when Nitro has that option.
Logger crashes on a defined DEBUG (@workflow/core). Nitro's dev build replaces process.env.DEBUG with its boolean debug option, so the bundled logger called true.split(',') and threw on the first log call. Non-string values now mean "no debug namespaces".

Verification

Unit tests: @workflow/nitro force-inline and moduleSideEffects behavior, plus the logger with a non-string DEBUG.
End to end against a published-package layout: packed workflow, @workflow/core, @workflow/nitro and @workflow/nuxt from this branch and installed them through pnpm overrides into a copy of the nuxt example. nuxt dev: the signup workflow runs to completed (it fails at fix 1 on npm 5.0.0). nuxt build + node server: still completed.

Not covered: Nitro v3 3.0.1-alpha.1 also restricts moduleSideEffects, but it matches entries against absolute module ids, so package-name prefixes don't reach it. Current Nitro v3 betas no longer restrict tree-shaking this way, and upgrading nitro fixes it.

🤖 Generated with Claude Code

In dev, workflow:force-inline bundles workflow packages so the SWC transform reaches them. With packages installed from npm (rather than workspace links) three things broke nuxt dev: - Relative imports inside an installed package (./run.js from lifecycle-hooks.js) were left to nitro:externals, which externalized a file Rollup had already inlined, aborting the build. - nitropack treats modules as side-effect free unless listed in moduleSideEffects, so the bundled world-init registration was dropped. - Nitro defines process.env.DEBUG as a boolean, which the core logger called .split() on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

vercel · 2026-10-01T01:37:18Z

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

Project	Deployment	Actions	Updated
example-nextjs-workflow-turbopack	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
example-nextjs-workflow-webpack	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
example-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-astro-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-express-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-fastify-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-hono-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-nestjs-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-nitro-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-nuxt-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-python-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-sveltekit-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-tanstack-start-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workbench-vite-workflow	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workflow-docs	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workflow-swc-playground	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workflow-tarballs	Ready	Preview, v0	Oct 1, 2026 1:40am UTC
workflow-web	Ready	Preview, v0	Oct 1, 2026 1:40am UTC

changeset-bot · 2026-10-01T01:37:19Z

🦋 Changeset detected

Latest commit: 31a01a6

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/nitro	Patch
@workflow/core	Patch
@workflow/nuxt	Patch
workflow	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/next	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
@workflow/world-testing	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/world-vercel	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 · 2026-10-01T01:37:32Z

📊 Workflow Benchmarks

commit 31a01a6 · Thu, 01 Oct 2026 02:04:23 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	348 (-12%)	2494 🔴 (+28%) 🔻	2599 🔴 (+14%)	2948 🔴 (+23%) 🔻	30
TTFS	stream	388 (+0.8%)	2426 🔴 (+26%) 🔻	2496 🔴 (+25%) 🔻	2923 🔴 (+22%) 🔻	30
TTFS	hook + stream	574 (-9.5%)	2736 🔴 (+22%) 🔻	2766 🔴 (+20%) 🔻	2899 🔴 (+22%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	536 (+12%)	912 (+26%) 🔻	1063 (+30%) 🔻	2872 (+21%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	1784 (-6.2%)	4893 (-12%)	5869 (-18%) 💚	9282 (-23%) 💚	10
STSO	1020 steps (inline)	108 (-29%) 💚	201 (-6.9%)	237 (-10%)	330 (-38%) 💚	1019
WO	1020 steps	197971 (-8.9%)	197971 (-8.9%)	197971 (-8.9%)	197971 (-8.9%)	1
CRTT	first chunk (pooled)	76 (+17%) 🔻	136 (+25%) 🔻	365 (+125%) 🔻	3330 (+1029%) 🔻	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	107 (+16%)	161 (-17%)	346 (-25%)	557 (-28%)	232 (-17%)	10
size sweep (100/s, 160B-12KB)	111 (+10%)	158 (-28%)	192 (-67%)	355 (-76%)	160 (-38%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	112 (+3%)	144 (-21%)	174 (-49%)	303 (-76%)	194 (-75%)	3
replay eve-gpt-5.6-sol-2000t (1x)	1766 (+731%)	210 (+14%)	2747 (+937%)	4049 (+514%)	3902 (+565%)	2
replay eve-gpt-5.6-sol-2000t (2x)	95 (+3%)	194 (-94%)	271 (-96%)	412 (-95%)	313 (-89%)	3

📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 216942ms → this run 197635ms (Δ -19307ms, -9%)

  100-150 ms  ┃                         main   0  this   1    +1
  150-200 ms  ███████████████████░░░░┃  main 581  this 753  +172
  200-250 ms  █████┃████                main 315  this 187  -128
  250-300 ms  █┃                        main  65  this  50   -15
  300-350 ms  ┃                         main  23  this  22    -1
  350-400 ms  ┃                         main  14  this   3   -11
  400-450 ms  ┃                         main   7  this   2    -5
  450-500 ms  ┃                         main   1  this   0    -1
  500-550 ms  ┃                         main   4  this   0    -4
  550-600 ms  ┃                         main   2  this   1    -1
  600-650 ms  ┃                         main   1  this   0    -1
  650-700 ms  ┃                         main   1  this   0    -1
  700-750 ms  ┃                         main   3  this   0    -3
  900-950 ms  ┃                         main   1  this   0    -1
1950-2000 ms  ┃                         main   1  this   0    -1

📈 CRTT drill-down vs main (RTT distributions & profiles)

variant  RTT 1ms→5s+              avg         p50           p90           p99     n
control  ······▃█▂▁···   150.1 (-13%)  123 (-16%)    346 (-25%)    557 (-28%)  3000
sweep    ······▂█▁····   134.7 (-31%)  128 (-15%)    192 (-67%)    355 (-76%)  3000
gw 1x    ·····▁▄█▁····     124 (-33%)  117 (-15%)    174 (-49%)    303 (-76%)  5295
eve 1x   ·····▁▃█▂▁▁▂·  467.8 (+179%)   126 (-9%)  2747 (+937%)  4049 (+514%)  5186
eve 2x   ······▂█▃▁···   157.1 (-86%)  140 (-39%)    271 (-96%)    412 (-95%)  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  ▇▃▅▆█▂▃▁▁▄  124–185ms
sweep    ▇▄▃█▁▂▁▂▁▁  125–156ms
gw 1x    █▂▁▂▄▃▂▅▄▄  116–138ms
eve 1x   █▇▁▁▁▁▁▃▆▁  129–1311ms
eve 2x   ▂▁█▃▁▂▅█▇▆  131–185ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ▃▇█▆▃▁▂  133–137ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▂▄▅█▃▃▃▁▃▄  35–61ms
sweep    ▁█▇▆▇▂▅▄▄▅  50–64ms
gw 1x    ▇▄▃▁▃█▆█▆█  32–42ms
eve 1x   ██▁▂▂▁▁▄▁▂  22–80ms
eve 2x   ▅▄▇▃▇▃▂▁▆█  20–31ms

ℹ️ Metric definitions & methodology

_{Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.}

_{The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.}

_{The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.}

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles}

_{Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600}

_{All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).}

_{Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.}

github-actions · 2026-10-01T01:37:32Z

🧪 E2E Test Results

✅ All tests passed

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

a run can take over its own earlier hook (sveltekit · local-dev / local / node / stable)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 01:42:00Z · abandoned wrun_01M3THZVMMMQJC73300YEXHC43
cold-start-warmup · suite warmup (tanstack-start) · at 01:42:08Z · abandoned wrun_01M3THZVN1KTSV6JWM4JQRD1KB
run-pickup-stall · hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-webpack) · at 01:50:13Z · abandoned wrun_01M3TJEWS8YB5H92GXQ9NGTYQR
run-pickup-stall · hookGetConflictWorkflow - awaiting hook.getConflict() registers hook without payload (nextjs-webpack) · at 01:50:15Z · abandoned wrun_01M3TJEYFEVH9ARDX605T18B4C

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3904	875	4779
✅ 💻 Local Development	4406	550	4956
✅ 📦 Local Production	4406	550	4956
✅ 🐘 Local Postgres	4406	550	4956
✅ 🪟 Windows	342	12	354
✅ 🌐 Cross-language Conformance	68	84	152
✅ dynamic-runs	0	0	0
✅ vercel-http-transport	879	183	1062
✅ vercel-multi-region	27	0	27
✅ vercel-ws-transport	595	113	708
Total	19033	2917	21950

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	142	35
✅ astro-quickjs	142	35
✅ example-node	142	35
✅ example-quickjs	142	35
✅ express-node	142	35
✅ express-quickjs	142	35
✅ fastify-node	142	35
✅ fastify-quickjs	142	35
✅ hono-node	142	35
✅ hono-quickjs	142	35
✅ nest-node	142	35
✅ nest-quickjs	142	35
✅ nextjs-turbopack-node	169	8
✅ nextjs-turbopack-quickjs	169	8
✅ nextjs-webpack-node	169	8
✅ nextjs-webpack-quickjs	169	8
✅ nitro-node	142	35
✅ nitro-quickjs	142	35
✅ nuxt-node	142	35
✅ nuxt-quickjs	142	35
✅ python-node	66	111
✅ sveltekit-node	161	16
✅ sveltekit-quickjs	161	16
✅ tanstack-start-node	142	35
✅ tanstack-start-quickjs	142	35
✅ vite-node	142	35
✅ vite-quickjs	142	35

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	171	0	6
✅ nextjs-turbopack-quickjs	171	0	6

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	84

✅ dynamic-runs

App	Passed	Failed	Skipped
✅ astro-vercel	0	0	0
✅ example-vercel	0	0	0
✅ express-vercel	0	0	0
✅ fastify-vercel	0	0	0
✅ hono-vercel	0	0	0
✅ nest-vercel	0	0	0
✅ nextjs-turbopack-vercel	0	0	0
✅ nextjs-webpack-vercel	0	0	0
✅ nitro-vercel	0	0	0
✅ nuxt-vercel	0	0	0
✅ sveltekit-vercel	0	0	0
✅ tanstack-start-vercel	0	0	0
✅ vite-vercel	0	0	0

✅ vercel-http-transport

App	Passed	Skipped
✅ example	142	35
✅ express	142	35
✅ hono	142	35
✅ nextjs-turbopack	169	8
✅ nitro	142	35
✅ vite	142	35

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	142	35
✅ express	142	35
✅ nextjs-turbopack	169	8
✅ vite	142	35

📋 View full workflow run

github-actions · 2026-10-01T01:41:12Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 42 total

fence=per-spec

scenario	outcome	events	virt	replay
✅ `smoke-no-steps`	completed	3	0ms	ok
✅ `smoke-one-step`	completed	6	0ms	ok
✅ `hook-at-step-started`	completed	12	0ms	ok
✅ `hook-at-step-completed`	completed	12	0ms	ok
✅ `hook-at-hook-created`	completed	12	0ms	ok
✅ `deadline-hook-wins`	completed	7	1.0h	ok
✅ `deadline-expires`	completed	7	1.0h	ok
✅ `step-vs-timer-early-settlement`	completed	8	1.0h	ok
✅ `long-sleep`	completed	11	30.0d	ok
✅ `hook-never-arrives`	stalled	3	0ms	skipped
✅ `step-retries-twice`	completed	10	2.0s	ok
✅ `parallel-steps`	completed	9	0ms	ok
✅ `hook-on-execution-state`	completed	12	0ms	ok
✅ `peek-hook-before-branch`	completed	12	0ms	ok
✅ `peek-hook-after-branch`	completed	12	0ms	ok
✅ `peek-hook-at-registration`	completed	12	0ms	ok
✅ `race-hook-before-probe`	completed	12	0ms	ok
✅ `race-hook-after-probe`	completed	12	0ms	ok
✅ `race-duplicate-delivery`	completed	13	0ms	ok
✅ `attr-hook-before-step`	completed	11	0ms	ok
✅ `attr-hook-after-step`	completed	11	0ms	ok
✅ `attr-from-step-body`	completed	13	0ms	ok
✅ `fork-hook-after-timeout`	completed	14	1.0m	ok
✅ `fork-hook-before-timeout`	completed	14	1.0m	ok
✅ `count-hook-after-timeout`	completed	17	1.0m	ok
✅ `count-hook-before-timeout`	completed	20	1.0m	ok
✅ `stale-read-step-count-fork`	completed	20	1.0m	ok
✅ `stale-read-equal-step-counts`	completed	14	1.0m	ok
✅ `step-vs-step-fork`	completed	12	0ms	ok
✅ `step-vs-step-fork-fenced`	completed	12	0ms	ok
✅ `fence-catches-benign-direction`	completed	12	5ms	ok
✅ `in-flight-before-decision`	completed	17	1.0m	ok
❌ `in-flight-before-decision-counted`	completed	17	1.0m	ok
✅ `in-flight-after-decision`	completed	19	2.0m	ok
✅ `stale-read-step-count-fork-fenced`	completed	20	1.0m	ok
✅ `fork-hook-wins`	completed	13	1.0m	ok
✅ `fork-timeout-wins`	completed	13	1.0m	ok
✅ `unclaimed-payload-under-fork`	completed	17	1.0m	ok
✅ `claimed-payload-under-fork`	completed	17	1.0m	ok
✅ `writers-independent-step-bodies`	completed	12	0ms	ok
✅ `writers-scripted-tempo`	completed	12	0ms	ok
✅ `cancel-mid-step`	cancelled	7	0ms	skipped

Full trace: world-sim.txt

github-actions · 2026-10-01T01:41:52Z

Framework	Flow route	Step reg.	Framework output
hono	265.9 KiB (±0)	97.2 KiB (±0)	1.99 MiB (+7 B)
nextjs-turbopack	273.3 KiB (±0)	426 B (±0)	981.6 KiB (+3 B)

About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

31a01a6 · run

karthikscale3

Reviewed the published-package bundling fix. The relative-import inlining is narrowly scoped, the Nitro v2 side-effect handling matches Nitro's resolver behavior, and the non-string DEBUG guard is safe. Targeted tests pass; no blocking issues found.

github-actions · 2026-10-01T04:40:59Z

No backport to stable for e915eab (AI decision).

Two of the three fixes target the workflow:force-inline dev-bundling plugin in @workflow/nitro, which does not exist on stable (git show origin/stable:packages/nitro/src/index.ts has no force-inline plugin and no externals interception), so the Rollup "already an existing non-external module id" error and the tree-shaken world-init registration are main-only failure modes. The third change, hardening matchesDebugNamespace in packages/core/src/logger.ts against a non-string process.env.DEBUG, is a genuine crash fix in a file that does exist on stable, but it is only reachable because Nitro's dev build inlines core — which again requires the main-only plugin. A human could split out the logger guard and force it through if defensive hardening there is wanted.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

e915eab3ea98d300e6431ad005c766c90b81695c

vercel Bot deployed to Preview – workflow-docs October 1, 2026 01:39 View deployment

VaguelySerious marked this pull request as ready for review October 1, 2026 02:01

VaguelySerious requested a review from a team as a code owner October 1, 2026 02:01

karthikscale3 approved these changes Oct 1, 2026

View reviewed changes

VaguelySerious merged commit e915eab into main Oct 1, 2026
322 of 325 checks passed

VaguelySerious deleted the peter/nitro-dev-published-packages branch October 1, 2026 04:40

This was referenced Oct 1, 2026

Version Packages #4526

Merged

Version Packages Thegreatsura/workflow#1

Open

pranaygp mentioned this pull request Oct 1, 2026

Upgrade Workflow SDK examples to 5.0.0 vercel/workflow-examples#53

Closed

VaguelySerious mentioned this pull request Oct 1, 2026

Update all examples to workflow 5.0.1 vercel/workflow-examples#52

Merged

Navigation Menu

Repository navigation

[nitro] Fix Nitro v2 dev builds against installed workflow packages - #4551

[nitro] Fix Nitro v2 dev builds against installed workflow packages#4551
VaguelySerious merged 1 commit into
mainfrom
peter/nitro-dev-published-packages

VaguelySerious commented Oct 1, 2026

Uh oh!

vercel Bot commented Oct 1, 2026 •

edited

Loading

Uh oh!

changeset-bot Bot commented Oct 1, 2026

Uh oh!

github-actions Bot commented Oct 1, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 1, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

karthikscale3 left a comment

Uh oh!

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

VaguelySerious commented Oct 1, 2026

Verification

Uh oh!

vercel Bot commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

changeset-bot Bot commented Oct 1, 2026

🦋 Changeset detected

Uh oh!

github-actions Bot commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

Uh oh!

github-actions Bot commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 E2E Test Results

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

github-actions Bot commented Oct 1, 2026

Sim World

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

karthikscale3 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Oct 1, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vercel Bot commented Oct 1, 2026 •

edited

Loading

github-actions Bot commented Oct 1, 2026 •

edited

Loading

github-actions Bot commented Oct 1, 2026 •

edited

Loading