Fix Nitro cleanup for React Router and add setup guides#2908
Conversation
🦋 Changeset detectedLatest commit: fbb8267 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 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 |
🧪 E2E Test Results✅ All tests passed Summary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
✅ vercel-multi-region
|
📊 Workflow Benchmarkscommit Backend:
📜 Previous results (3)b2e31a0Tue, 14 Jul 2026 00:24:00 GMT · run logs
e506f40Mon, 13 Jul 2026 23:04:58 GMT · run logs
02e7587Mon, 13 Jul 2026 22:34:08 GMT · run logs
Avg deltas compare against the most recent benchmark run on Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader) Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges 🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120 TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request. |
|
Backport PR opened against |
Summary
Fix React Router v7 and v8 production builds with Nitro v3, and add setup guides for both versions.
React Router creates a temporary Vite server during
vite build. Its Nitro server and Workflow's esbuild contexts remained active, so the build finished but did not exit. This PR cleans up both after their output is written.Testing
@workflow/nitrobuild and 32 testsDocs Preview
Closes #821