Version Packages (beta)#1787
Conversation
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests📋 Other (2 failed)e2e-local-postgres-nest-stable (2 failed):
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 10 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 25 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 50 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 10 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro workflow with 25 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 50 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) stream pipeline with 5 transform steps (1MB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro 10 parallel streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express fan-out fan-in 10 streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
aae4c5a to
377ad9e
Compare
db9fc7e to
8cfd0ac
Compare
8cfd0ac to
c8807a4
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@workflow/[email protected]
Major Changes
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.@workflow/[email protected]
Minor Changes
e295baeThanks @pranaygp! - Allowstart()to be called directly inside workflow functions[email protected]
Minor Changes
e295baeThanks @pranaygp! - Allowstart()to be called directly inside workflow functionsPatch Changes
417c493,e295bae]:@workflow/[email protected]
Patch Changes
#1544
3f6d98fThanks @iNishant! - Forwardstrict,inputExamples, andproviderOptionstool properties to language model providers, and handletype: 'dynamic'toolsUpdated dependencies [
e295bae]:@workflow/[email protected]
Patch Changes
417c493]:@workflow/[email protected]
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493,e295bae]:@workflow/[email protected]
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493,e295bae]:@workflow/[email protected]
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493]:@workflow/[email protected]
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493,e295bae]:@workflow/[email protected]
Patch Changes
417c493,e295bae]:@workflow/[email protected]
Patch Changes
@workflow/[email protected]
Patch Changes
#1686
417c493Thanks @TooTallNate! - BREAKING CHANGE: Removeclienttransform mode from SWC plugin. Theclientandstepmodes were nearly identical — both preserved step function bodies, replaced workflow bodies with throw stubs, and emitted the same JSON manifest. The only differences were the step registration mechanism (simple property assignment vs. IIFE) and whether DCE ran. Step mode now absorbs all client-mode behaviors: hoisted variable references for object property steps (so.stepIdis accessible), and dead code elimination. All integrations that previously usedmode: 'client'now usemode: 'step'.Updated dependencies [
417c493]:@workflow/[email protected]
Patch Changes
417c493]:@workflow/[email protected]
Patch Changes
417c493]:@workflow/[email protected]
Patch Changes
417c493,e295bae]:@workflow/[email protected]
Patch Changes
e295bae]:@workflow/[email protected]
Patch Changes
417c493,e295bae]:@workflow/[email protected]