Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
📊 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: Next.js (Turbopack) | Nitro | Express workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests🌍 Community Worlds (17 failed)mongodb (1 failed):
redis (1 failed):
starter (14 failed):
turso (1 failed):
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
|
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Description
This is, I hope, a beginning of a journey to have world class error messages. It's easy to think of the happy path when we build exciting things, but if not handled correctly and with care, the sad path is indeed sad and weird.
Example:
The idea is to have structure based on Wix's blog post about the subject that encapsulates a good error into multiple requirements:
I also added an ansi output helper to
@workflow/errorsso we can reuse it everywhere and provide structure to the errors so you know that a set of multiline strings are indeed related.How did you test your changes?
with the hono example:
xh POST 'localhost:3000/.well-known/workflow/v1/step' x-vqs-queue-name:__wkf_step_step//my-file.ts//stepName x-vqs-message-id:msg_hello x-vqs-message-attempt:1 stepId=step_abc123 workflowName=mywf workflowRunId=wrun_123 workflowStartedAt:=$(Date_now)PR Checklist - Required to merge
pnpm changesetwas run to create a changelog for this PRpnpm changeset --emptyif you are changing documentation or workbench appsgit commit --signoffon your commits)