docs(start): troubleshoot Cloudflare deployment config - #8396
tannerlinsley wants to merge 1 commit into
Conversation
|
View your CI Pipeline Execution ↗ for commit 6ec9f33
☁️ Nx Cloud last updated this comment at |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe PR adds Cloudflare Workers deployment troubleshooting guidance for React Start and an end-to-end test that validates Wrangler dry-run output against the generated server configuration. ChangesCloudflare deployment validation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The PR adds troubleshooting guidance and dry-run coverage without introducing a concrete deployment risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 Changeset Version Preview3 package(s) bumped directly, 21 bumped as dependents. 🟩 Patch bumps
|
🎯 Changes
Explain why Cloudflare deployment can fail after a successful Vite build when
wrangler deploy --config wrangler.jsoncbypasses the generated deployment config. Show the build and dry-run commands, how to preserve generated output between CI jobs, and how to select a named environment at build time.The existing Cloudflare browser suite now includes a deployment dry run using the generated config. This addresses the configuration mistake reported in #5554 without adding an external-module workaround or changing the source server entry.
Validation: the explicit source-config dry run reproduced the missing-entry error; the generated-config dry run passed. All 4 Cloudflare preview/dry-run tests passed. A temporary staging config verified build-time environment selection and passed a dry run, then the source config and default build were restored. Required lint, type, unit, and formatting checks passed. No Worker was published, and live account permissions or deployed bindings were not tested.
✅ Checklist
🚀 Release Impact
Summary by CodeRabbit
Documentation
Tests