Skip to content

Fix published package sourcemaps for npm consumers#1769

Merged
TooTallNate merged 1 commit intomainfrom
tomdale/fix-package-sourcemaps
Apr 16, 2026
Merged

Fix published package sourcemaps for npm consumers#1769
TooTallNate merged 1 commit intomainfrom
tomdale/fix-package-sourcemaps

Conversation

@tomdale
Copy link
Copy Markdown
Contributor

@tomdale tomdale commented Apr 16, 2026 •
edited
Loading

Fix published package sourcemaps for npm consumers

Summary

Downstream Vite and Vitest users can currently hit warnings like Sourcemap for ".../dist/*.js" points to missing source files when @workflow/* packages are inlined during tests. The published packages were shipping sourcemaps that pointed at ../src/*.ts, but the matching source files were not present in the npm tarball and the maps did not embed sourcesContent.

This left workflow in an unusable middle state for consumers: sourcemaps were published, but they were not self-contained and the referenced sources were absent.

Root cause

The shared package TypeScript base config enabled sourceMap, but it set inlineSources to false. Packages that publish dist/ without publishing src/ therefore emitted .js.map files that referenced ../src/*.ts paths with no embedded source content. Vite eagerly reads those maps, so it warns once per affected file.

What changed

  • Enabled inlineSources in packages/tsconfig/base.json.
  • Kept the fix at the shared build layer so it applies consistently across the published packages that inherit this config.
  • Left package files entries unchanged. The fix comes from making the published JavaScript sourcemaps self-contained rather than suppressing warnings in consumers or expanding npm tarballs to include every src/ tree.
  • Added a patch changeset for the published packages whose tarballs pick up this shared sourcemap change:
    workflow, @workflow/ai, @workflow/astro, @workflow/builders, @workflow/cli, @workflow/core, @workflow/errors, @workflow/next, @workflow/nitro, @workflow/nuxt, @workflow/rollup, @workflow/serde, @workflow/sveltekit, @workflow/typescript-plugin, @workflow/utils, @workflow/vite, @workflow/vitest, @workflow/world-local, @workflow/world-postgres, @workflow/world-testing, and @workflow/world-vercel.

Packages with existing inline JS sourcemaps such as @workflow/core and workflow keep that shape, but their embedded maps now also carry source content. Packages that ship external .js.map files such as @workflow/builders, @workflow/rollup, and @workflow/vitest now publish those maps with sourcesContent.

This follows the internal vercel/ai precedent of shipping usable sourcemaps to npm consumers instead of asking consumers to suppress warnings. Other Vercel OSS packages like swr, serve, and @vercel/ncc avoid this class of problem by not publishing sourcemaps at all. Since workflow already publishes sourcemaps, embedding source content is the narrowest fix that makes those published maps usable.

Validation

Commands run:

  • pnpm --filter @workflow/core --filter @workflow/builders --filter @workflow/rollup --filter @workflow/vitest build
  • pnpm --filter @workflow/utils --filter @workflow/errors --filter @workflow/world-local --filter @workflow/world-vercel --filter @workflow/serde build
  • pnpm pack --pack-destination /tmp/workflow-pack in packages/core, packages/builders, packages/rollup, and packages/vitest
  • direct inspection of emitted .map files in dist/ and packaged tarball contents under /tmp/workflow-pack

@tomdale
fix(packaging): embed source content in sourcemaps
6a051d4 
Enable TypeScript inlineSources in the shared package tsconfig so published @workflow packages ship self-contained JavaScript sourcemaps. This fixes Vite and Vitest warnings in downstream repos when sourcemaps point at ../src/*.ts paths that are not published.
@tomdale tomdale requested a review from a team as a code owner April 16, 2026 05:28
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 16, 2026

🦋 Changeset detected

Latest commit: 6a051d4

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

This PR includes changesets to release 24 packages
Name Type
@workflow/ai Patch
@workflow/astro Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/core Patch
@workflow/errors Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/nuxt Patch
@workflow/rollup Patch
@workflow/serde Patch
@workflow/sveltekit Patch
@workflow/typescript-plugin Patch
@workflow/utils Patch
@workflow/vite Patch
@workflow/vitest Patch
@workflow/world-local Patch
@workflow/world-postgres Patch
@workflow/world-testing Patch
@workflow/world-vercel Patch
workflow Patch
@workflow/nest Patch
@workflow/web-shared Patch
@workflow/web Patch

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

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

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 16, 2026 •
edited
Loading

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

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Apr 16, 2026 5:29am
example-nextjs-workflow-webpack Ready Ready Preview, Comment Apr 16, 2026 5:29am
example-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-astro-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-express-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-fastify-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-hono-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-nitro-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-nuxt-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-sveltekit-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workbench-vite-workflow Ready Ready Preview, Comment Apr 16, 2026 5:29am
workflow-swc-playground Ready Ready Preview, Comment Apr 16, 2026 5:29am
workflow-web Ready Ready Preview, Comment Apr 16, 2026 5:29am

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 16, 2026 •
edited
Loading

📊 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 🥇 Express 0.044s (+24.9% 🔺) 1.005s (~) 0.962s 10 1.00x
🐘 Postgres Nitro 0.069s (+13.3% 🔺) 1.022s (+1.2%) 0.953s 10 1.57x
🐘 Postgres Express 0.074s (+1.8%) 1.020s (~) 0.947s 10 1.68x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.245s (-29.6% 🟢) 2.577s (+19.3% 🔺) 2.332s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.419s (+68.7% 🔺) 2.157s (~) 1.738s 10 1.71x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.124s (+2.3%) 2.006s (~) 0.881s 10 1.00x
🐘 Postgres Nitro 1.153s (+1.2%) 2.008s (~) 0.855s 10 1.03x
🐘 Postgres Express 1.154s (~) 2.010s (~) 0.856s 10 1.03x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.148s (+12.8% 🔺) 3.722s (+3.3%) 1.574s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.148s (+14.6% 🔺) 3.536s (-1.5%) 1.387s 10 1.00x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 10.867s (~) 11.022s (~) 0.155s 3 1.00x
💻 Local Express 10.911s (+2.4%) 11.023s (~) 0.111s 3 1.00x
🐘 Postgres Express 10.918s (-0.6%) 11.023s (-2.9%) 0.105s 3 1.00x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 17.326s (+2.0%) 19.590s (+1.9%) 2.265s 2 1.00x
▲ Vercel Next.js (Turbopack) 19.762s (+11.7% 🔺) 21.528s (+10.4% 🔺) 1.767s 2 1.14x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 14.492s (-0.8%) 15.025s (~) 0.534s 4 1.00x
🐘 Postgres Nitro 14.560s (~) 15.025s (~) 0.465s 4 1.00x
💻 Local Express 15.224s (+6.9% 🔺) 16.031s (+6.7% 🔺) 0.807s 4 1.05x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 31.506s (-4.9%) 33.442s (-4.9%) 1.936s 2 1.00x
▲ Vercel Next.js (Turbopack) 31.930s (-2.6%) 33.567s (-3.0%) 1.637s 2 1.01x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 13.829s (-3.5%) 14.024s (-6.7% 🟢) 0.195s 7 1.00x
🐘 Postgres Nitro 13.906s (~) 14.307s (+2.0%) 0.401s 7 1.01x
💻 Local Express 17.324s (+16.2% 🔺) 18.033s (+20.0% 🔺) 0.709s 5 1.25x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 53.913s (+2.6%) 55.414s (+2.4%) 1.502s 2 1.00x
▲ Vercel Next.js (Turbopack) 54.428s (-3.0%) 56.401s (-2.2%) 1.973s 2 1.01x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.255s (-0.8%) 2.008s (~) 0.752s 15 1.00x
🐘 Postgres Express 1.274s (-1.4%) 2.009s (~) 0.734s 15 1.02x
💻 Local Express 1.538s (+5.4% 🔺) 2.006s (~) 0.468s 15 1.23x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.161s (~) 3.783s (+1.9%) 1.623s 8 1.00x
▲ Vercel Express 2.624s (+1.1%) 4.595s (+9.0% 🔺) 1.972s 7 1.21x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 2.335s (-0.8%) 3.007s (~) 0.672s 10 1.00x
🐘 Postgres Nitro 2.354s (+0.7%) 3.009s (~) 0.655s 10 1.01x
💻 Local Express 2.881s (+1.4%) 3.209s (+3.2%) 0.327s 10 1.23x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.734s (-11.7% 🟢) 4.051s (-12.2% 🟢) 1.318s 8 1.00x
▲ Vercel Express 3.027s (+20.7% 🔺) 4.552s (+19.4% 🔺) 1.525s 7 1.11x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.466s (~) 4.015s (~) 0.549s 8 1.00x
🐘 Postgres Express 3.499s (+0.5%) 4.010s (~) 0.510s 8 1.01x
💻 Local Express 8.371s (+18.0% 🔺) 9.027s (+12.6% 🔺) 0.656s 4 2.42x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.820s (-1.6%) 4.555s (+3.5%) 1.735s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.258s (-17.7% 🟢) 4.842s (-14.2% 🟢) 1.585s 7 1.16x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.266s (+0.5%) 2.008s (~) 0.743s 15 1.00x
🐘 Postgres Express 1.267s (+0.8%) 2.007s (~) 0.740s 15 1.00x
💻 Local Express 1.557s (+5.8% 🔺) 2.006s (~) 0.449s 15 1.23x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.326s (+4.8%) 3.683s (-3.6%) 1.356s 9 1.00x
▲ Vercel Express 4.254s (+102.4% 🔺) 6.016s (+66.0% 🔺) 1.762s 5 1.83x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 2.329s (~) 3.009s (~) 0.680s 10 1.00x
🐘 Postgres Express 2.344s (~) 3.009s (~) 0.666s 10 1.01x
💻 Local Express 2.890s (+7.2% 🔺) 3.453s (+14.8% 🔺) 0.563s 9 1.24x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.665s (-6.8% 🟢) 4.305s (-0.8%) 1.640s 7 1.00x
▲ Vercel Next.js (Turbopack) 2.978s (-8.2% 🟢) 4.528s (-7.5% 🟢) 1.550s 7 1.12x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.475s (~) 4.008s (~) 0.533s 8 1.00x
🐘 Postgres Express 3.478s (~) 4.009s (~) 0.531s 8 1.00x
💻 Local Express 8.753s (+14.4% 🔺) 9.027s (+12.6% 🔺) 0.274s 4 2.52x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.342s (-25.7% 🟢) 4.926s (-18.1% 🟢) 1.584s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.358s (-20.6% 🟢) 5.135s (-10.6% 🟢) 1.777s 6 1.00x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 10 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.779s (-8.0% 🟢) 1.006s (-1.7%) 0.227s 60 1.00x
🐘 Postgres Nitro 0.812s (~) 1.023s (~) 0.210s 59 1.04x
💻 Local Express 1.004s (+41.2% 🔺) 1.505s (+47.4% 🔺) 0.501s 40 1.29x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 9.327s (-3.6%) 11.098s (-3.2%) 1.771s 6 1.00x
▲ Vercel Next.js (Turbopack) 10.004s (-17.9% 🟢) 11.890s (-16.2% 🟢) 1.885s 6 1.07x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 25 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.898s (-1.7%) 2.052s (-2.3%) 0.155s 44 1.00x
🐘 Postgres Express 1.904s (-8.6% 🟢) 2.124s (-27.9% 🟢) 0.220s 43 1.00x
💻 Local Express 3.001s (+32.9% 🔺) 3.508s (+16.7% 🔺) 0.507s 26 1.58x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 28.992s (-4.5%) 30.695s (-5.2% 🟢) 1.703s 3 1.00x
▲ Vercel Next.js (Turbopack) 29.800s (-2.3%) 31.433s (-2.8%) 1.633s 3 1.03x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 50 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 3.822s (-7.2% 🟢) 4.043s (-17.4% 🟢) 0.220s 30 1.00x
🐘 Postgres Nitro 3.886s (~) 4.110s (~) 0.224s 30 1.02x
💻 Local Express 9.481s (+29.4% 🔺) 10.019s (+25.0% 🔺) 0.538s 12 2.48x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 75.918s (-42.1% 🟢) 77.696s (-41.7% 🟢) 1.778s 2 1.00x
▲ Vercel Next.js (Turbopack) 78.982s (-4.4%) 80.345s (-4.8%) 1.363s 2 1.04x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 10 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.287s (+0.7%) 1.007s (~) 0.720s 60 1.00x
🐘 Postgres Nitro 0.289s (~) 1.007s (~) 0.718s 60 1.01x
💻 Local Express 0.686s (+14.7% 🔺) 1.116s (+9.3% 🔺) 0.430s 54 2.39x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 1.616s (-4.0%) 3.355s (+2.5%) 1.739s 18 1.00x
▲ Vercel Express 1.765s (+10.0% 🔺) 3.542s (+7.8% 🔺) 1.777s 17 1.09x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

workflow with 25 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.484s (-2.1%) 1.006s (~) 0.522s 90 1.00x
🐘 Postgres Nitro 0.498s (-1.3%) 1.006s (~) 0.508s 90 1.03x
💻 Local Express 2.559s (+3.9%) 3.009s (~) 0.450s 30 5.29x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.923s (+8.1% 🔺) 4.647s (+9.9% 🔺) 1.724s 20 1.00x
▲ Vercel Next.js (Turbopack) 3.654s (+11.6% 🔺) 5.367s (+10.7% 🔺) 1.713s 17 1.25x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 50 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.785s (-3.3%) 1.007s (-1.0%) 0.222s 120 1.00x
🐘 Postgres Nitro 0.785s (-2.1%) 1.008s (~) 0.222s 120 1.00x
💻 Local Express 11.867s (+12.1% 🔺) 12.331s (+11.9% 🔺) 0.463s 10 15.11x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -
💻 Local Nitro ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 5.845s (-15.6% 🟢) 7.844s (-11.0% 🟢) 2.000s 17 1.00x
▲ Vercel Next.js (Turbopack) 6.945s (+6.9% 🔺) 8.471s (+1.1%) 1.526s 15 1.19x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.202s (-5.8% 🟢) 0.993s (~) 0.001s (~) 1.010s (~) 0.808s 10 1.00x
🐘 Postgres Express 0.207s (-3.6%) 0.997s (~) 0.002s (-6.3% 🟢) 1.010s (~) 0.803s 10 1.03x
💻 Local Express 0.211s (+49.7% 🔺) 1.005s (~) 0.012s (+30.9% 🔺) 1.019s (~) 0.808s 10 1.05x
💻 Local Next.js (Turbopack) ⚠️ missing - - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -
💻 Local Nitro ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 1.573s (+11.7% 🔺) 3.168s (+21.8% 🔺) 0.695s (-28.5% 🟢) 4.314s (+8.4% 🔺) 2.741s 10 1.00x
▲ Vercel Next.js (Turbopack) 1.883s (+26.3% 🔺) 3.248s (+7.1% 🔺) 1.045s (+31.1% 🔺) 4.698s (+10.6% 🔺) 2.815s 10 1.20x
▲ Vercel Nitro ⚠️ missing - - - - -

🔍 Observability: Express | Next.js (Turbopack)

stream pipeline with 5 transform steps (1MB)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.605s (-5.7% 🟢) 1.004s (~) 0.004s (-6.1% 🟢) 1.022s (~) 0.417s 59 1.00x
🐘 Postgres Nitro 0.611s (-1.2%) 1.004s (~) 0.004s (-3.0%) 1.024s (~) 0.413s 59 1.01x
💻 Local Express 0.928s (+39.1% 🔺) 1.034s (+2.3%) 0.013s (+40.8% 🔺) 1.142s (+2.5%) 0.214s 54 1.53x
💻 Local Next.js (Turbopack) ⚠️ missing - - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -
💻 Local Nitro ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 4.382s (+5.0% 🔺) 6.182s (~) 0.297s (-31.1% 🟢) 7.061s (~) 2.679s 9 1.00x
▲ Vercel Next.js (Turbopack) 4.700s (+11.5% 🔺) 6.105s (+0.6%) 0.353s (~) 7.092s (+3.7%) 2.392s 9 1.07x
▲ Vercel Nitro ⚠️ missing - - - - -

🔍 Observability: Express | Next.js (Turbopack)

10 parallel streams (1MB each)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.938s (-4.2%) 1.106s (-13.3% 🟢) 0.000s (-57.4% 🟢) 1.122s (-14.2% 🟢) 0.184s 54 1.00x
🐘 Postgres Express 0.968s (-1.2%) 1.164s (-2.8%) 0.000s (-3.8%) 1.181s (-2.9%) 0.213s 52 1.03x
💻 Local Express 1.378s (+16.8% 🔺) 2.025s (~) 0.001s (+77.8% 🔺) 2.027s (~) 0.649s 30 1.47x
💻 Local Next.js (Turbopack) ⚠️ missing - - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -
💻 Local Nitro ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.715s (-19.4% 🟢) 4.197s (-6.5% 🟢) 0.000s (-100.0% 🟢) 4.650s (-4.5%) 1.935s 14 1.00x
▲ Vercel Next.js (Turbopack) 3.049s (-7.1% 🟢) 4.335s (-4.3%) 0.000s (-93.8% 🟢) 4.815s (-4.0%) 1.766s 13 1.12x
▲ Vercel Nitro ⚠️ missing - - - - -

🔍 Observability: Express | Next.js (Turbopack)

fan-out fan-in 10 streams (1MB each)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 1.769s (~) 2.175s (+1.7%) 0.000s (-48.2% 🟢) 2.187s (+1.8%) 0.419s 28 1.00x
🐘 Postgres Nitro 1.775s (+2.1%) 2.141s (~) 0.000s (+100.0% 🔺) 2.161s (~) 0.386s 28 1.00x
💻 Local Express 3.946s (+12.5% 🔺) 4.539s (+12.6% 🔺) 0.000s (-42.9% 🟢) 4.542s (+12.6% 🔺) 0.595s 14 2.23x
💻 Local Next.js (Turbopack) ⚠️ missing - - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -
💻 Local Nitro ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 4.172s (+5.0%) 5.718s (+10.5% 🔺) 0.000s (-100.0% 🟢) 6.271s (+11.1% 🔺) 2.099s 10 1.00x
▲ Vercel Next.js (Turbopack) 4.284s (-0.6%) 5.473s (-3.4%) 0.000s (-9.1% 🟢) 5.848s (-3.8%) 1.564s 11 1.03x
▲ Vercel Nitro ⚠️ missing - - - - -

🔍 Observability: Express | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Express 21/21
🐘 Postgres Nitro 11/21
▲ Vercel Express 17/21
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 🐘 Postgres 16/21
Next.js (Turbopack) ▲ Vercel 21/21
Nitro 🐘 Postgres 21/21
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
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

❌ Some benchmark jobs failed:

  • Local: failure
  • Postgres: success
  • Vercel: failure

Check the workflow run for details.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 16, 2026 •
edited
Loading

🧪 E2E Test Results

❌ Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 923 0 67 990
✅ 💻 Local Development 994 0 86 1080
✅ 📦 Local Production 994 0 86 1080
✅ 🐘 Local Postgres 994 0 86 1080
✅ 🪟 Windows 90 0 0 90
❌ 🌍 Community Worlds 133 98 0 231
✅ 📋 Other 252 0 18 270
Total 4380 98 343 4821

❌ Failed Tests

🌍 Community Worlds (98 failed)

mongodb (15 failed):

  • readableStreamWorkflow | wrun_01KPACAS798AXHDER0W1P138A3
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KPACBEWYG515AS350QXDEFQV
  • webhookWorkflow | wrun_01KPACBQZP5Q7W75X43HT5T762
  • outputStreamWorkflow no startIndex (reads all chunks)
  • outputStreamWorkflow positive startIndex (skips first chunk)
  • outputStreamWorkflow negative startIndex (reads from end)
  • outputStreamWorkflow - getTailIndex and getChunks getTailIndex returns correct index after stream completes
  • outputStreamWorkflow - getTailIndex and getChunks getTailIndex returns -1 before any chunks are written
  • outputStreamWorkflow - getTailIndex and getChunks getChunks returns same content as reading the stream
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions | wrun_01KPACF7T4BA7MW623WXF9N2BV
  • fetchWorkflow | wrun_01KPACFNNAYFMGQ060AS1RV1KR
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KPACM5QQNB4D7X502QXWMSAK
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KPACVRZVVN7QNRQR3J9N4NH1

redis (15 failed):

  • readableStreamWorkflow | wrun_01KPACAS798AXHDER0W1P138A3
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KPACBEWYG515AS350QXDEFQV
  • webhookWorkflow | wrun_01KPACBQZP5Q7W75X43HT5T762
  • outputStreamWorkflow no startIndex (reads all chunks)
  • outputStreamWorkflow positive startIndex (skips first chunk)
  • outputStreamWorkflow negative startIndex (reads from end)
  • outputStreamWorkflow - getTailIndex and getChunks getTailIndex returns correct index after stream completes
  • outputStreamWorkflow - getTailIndex and getChunks getTailIndex returns -1 before any chunks are written
  • outputStreamWorkflow - getTailIndex and getChunks getChunks returns same content as reading the stream
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions | wrun_01KPACF7T4BA7MW623WXF9N2BV
  • fetchWorkflow | wrun_01KPACFNNAYFMGQ060AS1RV1KR
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KPACM5QQNB4D7X502QXWMSAK
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KPACVRZVVN7QNRQR3J9N4NH1

turso (68 failed):

  • addTenWorkflow | wrun_01KPACA70R7WAS25H1YPFZKDX9
  • addTenWorkflow | wrun_01KPACA70R7WAS25H1YPFZKDX9
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KPACAGXDJQ27BN82Q43TWWHC
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KPACADY3DHKKD69806J5N8NW
  • promiseRaceWorkflow | wrun_01KPACAKJ09RTTNTZMB550KQ74
  • promiseAnyWorkflow | wrun_01KPACAQ1AEYDEV4G2YB4GJECP
  • importedStepOnlyWorkflow | wrun_01KPACAXZT80GN19WYQSWKVWVS
  • readableStreamWorkflow | wrun_01KPACAS798AXHDER0W1P138A3
  • hookWorkflow | wrun_01KPACB2Y6YK5B38XRQ3T1Q152
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KPACBEWYG515AS350QXDEFQV
  • webhookWorkflow | wrun_01KPACBQZP5Q7W75X43HT5T762
  • sleepingWorkflow | wrun_01KPACBYSZ8SJQS2N0C2F5THN7
  • parallelSleepWorkflow | wrun_01KPACCAR4VQRMV987PZKXQ3N1
  • nullByteWorkflow | wrun_01KPACCE30EWNZGW93RVY8E03P
  • workflowAndStepMetadataWorkflow | wrun_01KPACCGBZDPZK7HPJY3FJJRDR
  • outputStreamWorkflow no startIndex (reads all chunks)
  • outputStreamWorkflow positive startIndex (skips first chunk)
  • outputStreamWorkflow negative startIndex (reads from end)
  • outputStreamWorkflow - getTailIndex and getChunks getTailIndex returns correct index after stream completes
  • outputStreamWorkflow - getTailIndex and getChunks getTailIndex returns -1 before any chunks are written
  • outputStreamWorkflow - getTailIndex and getChunks getChunks returns same content as reading the stream
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions | wrun_01KPACF7T4BA7MW623WXF9N2BV
  • fetchWorkflow | wrun_01KPACFNNAYFMGQ060AS1RV1KR
  • promiseRaceStressTestWorkflow | wrun_01KPACFT13NV76CGE3GQ0RN1WW
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KPACKGKNTWFXWT0NV504HTNS
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KPACM5QQNB4D7X502QXWMSAK
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KPACMX4HX82771QMJESBEWA8
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KPACNJXSJGNJG1W68BH8T2B8
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KPACNWWPZE92KZETQRP1R71H
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KPACP57RAGHKJZBE4DPQ1D76
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KPACP7T6FZKSWN33445XJFQ3
  • runClassSerializationWorkflow - Run instances serialize across workflow/step boundaries | wrun_01KPACPKRW320KXZX28WT9P2CE
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KPACQ42MPCHQD561X7Y2HN4E
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KPACQ9SH6V870PWSEC0BFDK1
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KPACQHKVSK25Q333280MSYKF
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KPACQTZGNT04BJZ3ETQ6WR92
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KPACR5NJ5BC55ZDFEVNJ2KP8
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KPACRF7K9CPNED4TS4JXEFG1
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KPACRP48C09TD1NECZMNZHTD
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KPACS1GM56MVRW66VQFXKWK0
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KPACS9GB9N9QV1BKHYR813G7
  • cancelRun - cancelling a running workflow | wrun_01KPACSHFJXWS11XY0VJGZ6JKY
  • cancelRun via CLI - cancelling a running workflow | wrun_01KPACSVB30W76E9KV7QKEDGV8
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KPACT7R44MFX648PAT2R13BS
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KPACTZA9QQYA0R70AJBQQRAZ
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KPACVA9CCB57CDAC4YN6M7R0
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KPACVKDTDGASSHGHVKMPGPYK
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577) | wrun_01KPACVNMVYJJ6J9R9RQ539GRK
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KPACVRZVVN7QNRQR3J9N4NH1
  • getterStepWorkflow - getter functions with "use step" directive | wrun_01KPACVYMX57NYFC2HHC49WWXT

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 83 0 7
✅ example 83 0 7
✅ express 83 0 7
✅ fastify 83 0 7
✅ hono 83 0 7
✅ nextjs-turbopack 88 0 2
✅ nextjs-webpack 88 0 2
✅ nitro 83 0 7
✅ nuxt 83 0 7
✅ sveltekit 83 0 7
✅ vite 83 0 7
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 84 0 6
✅ express-stable 84 0 6
✅ fastify-stable 84 0 6
✅ hono-stable 84 0 6
✅ nextjs-turbopack-canary 71 0 19
✅ nextjs-turbopack-stable 90 0 0
✅ nextjs-webpack-canary 71 0 19
✅ nextjs-webpack-stable 90 0 0
✅ nitro-stable 84 0 6
✅ nuxt-stable 84 0 6
✅ sveltekit-stable 84 0 6
✅ vite-stable 84 0 6
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 84 0 6
✅ express-stable 84 0 6
✅ fastify-stable 84 0 6
✅ hono-stable 84 0 6
✅ nextjs-turbopack-canary 71 0 19
✅ nextjs-turbopack-stable 90 0 0
✅ nextjs-webpack-canary 71 0 19
✅ nextjs-webpack-stable 90 0 0
✅ nitro-stable 84 0 6
✅ nuxt-stable 84 0 6
✅ sveltekit-stable 84 0 6
✅ vite-stable 84 0 6
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 84 0 6
✅ express-stable 84 0 6
✅ fastify-stable 84 0 6
✅ hono-stable 84 0 6
✅ nextjs-turbopack-canary 71 0 19
✅ nextjs-turbopack-stable 90 0 0
✅ nextjs-webpack-canary 71 0 19
✅ nextjs-webpack-stable 90 0 0
✅ nitro-stable 84 0 6
✅ nuxt-stable 84 0 6
✅ sveltekit-stable 84 0 6
✅ vite-stable 84 0 6
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 90 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 6 0 0
❌ mongodb 56 15 0
✅ redis-dev 6 0 0
❌ redis 56 15 0
✅ turso-dev 6 0 0
❌ turso 3 68 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 84 0 6
✅ e2e-local-postgres-nest-stable 84 0 6
✅ e2e-local-prod-nest-stable 84 0 6

📋 View full workflow run

TooTallNate
TooTallNate approved these changes Apr 16, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate left a comment

Choose a reason for hiding this comment

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

One-line fix in the right place. Flipping inlineSources from false to true in the shared tsconfig makes published sourcemaps self-contained by embedding the original TypeScript source in sourcesContent. This eliminates "points to missing source files" warnings for downstream Vite/Vitest consumers without changing package files entries or expanding tarballs with src/ trees.

Changeset correctly lists all 22 published packages that inherit this config. The tarball size increase from embedded source content is a reasonable trade-off — the maps were already being shipped, they just pointed at files that did not exist in the tarball.

@TooTallNate TooTallNate added the backport-stable Cherry-pick this PR to the stable branch when merged label Apr 16, 2026
@TooTallNate TooTallNate merged commit 5a42964 into main Apr 16, 2026
108 of 110 checks passed
@TooTallNate TooTallNate deleted the tomdale/fix-package-sourcemaps branch April 16, 2026 07:21
@workflow-devkit-release-bot
Copy link
Copy Markdown
Contributor

workflow-devkit-release-bot bot commented Apr 16, 2026

Backported to stable (5a42964 -> 6f48e9e).

workflow-devkit-release-bot bot pushed a commit that referenced this pull request Apr 16, 2026
@tomdale
fix(packaging): embed source content in sourcemaps (#1769)
6f48e9e 
Enable TypeScript inlineSources in the shared package tsconfig so published @workflow packages ship self-contained JavaScript sourcemaps. This fixes Vite and Vitest warnings in downstream repos when sourcemaps point at ../src/*.ts paths that are not published.
@workflow-devkit-release-bot workflow-devkit-release-bot bot mentioned this pull request Apr 16, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@TooTallNate TooTallNate TooTallNate approved these changes

Assignees

No one assigned

Labels

backport-stable Cherry-pick this PR to the stable branch when merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@tomdale @TooTallNate