Fix CLI health check for Astro/Sveltekit and add debug http logs to world-vercel#1442
Merged
Conversation
When DEBUG=workflow:* is set: 1. Runtime emits timing logs for each event page load (page number, event count, ms) and total event loading (total events, pages, ms). 2. World-vercel emits timing logs for every HTTP request to workflow-server (method, endpoint, status code, duration ms). These logs help diagnose performance issues in the V2 inline execution loop, such as slow event loading or high-latency API calls. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The CLI's getEnvVars() function reads a fixed list of env vars but was missing WORKFLOW_LOCAL_BASE_URL. The health check command defaults to port 3000 when this var is absent. Frameworks that use non-standard ports (Astro: 4321, SvelteKit: 5173) need this env var to be read for the health check to connect to the correct port. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 9c390e2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 17 packages
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 |
Contributor
VaguelySerious
commented
Mar 18, 2026
| WORKFLOW_VERCEL_PROJECT: env.WORKFLOW_VERCEL_PROJECT || '', | ||
| WORKFLOW_VERCEL_PROJECT_NAME: env.WORKFLOW_VERCEL_PROJECT_NAME || '', | ||
| WORKFLOW_VERCEL_TEAM: env.WORKFLOW_VERCEL_TEAM || '', | ||
| WORKFLOW_LOCAL_BASE_URL: env.WORKFLOW_LOCAL_BASE_URL || '', |
Member
Author
There was a problem hiding this comment.
The CLI's getEnvVars() function reads a fixed list of env vars but was
missing WORKFLOW_LOCAL_BASE_URL. The health check command defaults to
port 3000 when this var is absent. Frameworks that use non-standard
ports (Astro: 4321, SvelteKit: 5173) need this env var to be read
for the health check to connect to the correct port.
Contributor
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (2 failed)nitro (2 failed):
🐘 Local Postgres (1 failed)fastify-stable (1 failed):
🌍 Community Worlds (55 failed)mongodb (2 failed):
redis (2 failed):
turso (51 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
❌ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | 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 | Next.js (Turbopack) | Express Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
karthikscale3
approved these changes
Mar 18, 2026
Contributor
karthikscale3
left a comment
karthikscale3
left a comment
There was a problem hiding this comment.
Review
No functional regressions. All three changes are correct in behavior:
- The env.ts fix resolves a real bug for non-default-port frameworks
- Both debug logging additions are properly gated and don't affect production behavior
- The fetch timing wrapper doesn't alter the request/response flow
The only issue worth raising is the import ordering in world-vercel/src/utils.ts -- the new code should be moved below all imports to maintain code conventions and avoid potential lint failures.
pranaygp
reviewed
Mar 18, 2026
| ): void { | ||
| if (HTTP_DEBUG_ENABLED) { | ||
| console.debug( | ||
| `[workflow:world-vercel:http] ${method} ${endpoint} -> ${status} (${ms}ms)` |
Contributor
There was a problem hiding this comment.
(although I assumed we already had this 🤷🏼 )
pranaygp
approved these changes
Mar 18, 2026
ghost
mentioned this pull request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.