fix: router.handle -> router.fetch for itty-router v5#14
fix: router.handle -> router.fetch for itty-router v5#14chitcommit wants to merge 1 commit intomainfrom
Conversation
itty-router v5 renamed the dispatch method from handle() to fetch(). The old call hit the Proxy getter, created a phantom route entry, and returned undefined — causing the Worker to hang with 1101. Also switched from custom_domain to zone route to avoid routing conflicts (the custom domain + legacy route combo caused loops). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
chittyintel | 6477e09 | Mar 28 2026, 10:14 AM |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe request handling in the main entry point switches from calling Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Summary
router.handle()does not exist in itty-router v5 — it was renamed torouter.fetch()custom_domainto zone route to avoid routing conflictsAlready deployed
Fix is live on
intel.chitty.cc— health check returning 200.Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Summary by CodeRabbit