Repository navigation
Conversation
|
@johannschopplich is attempting to deploy a commit to the Nitro Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe change filters the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
commit: |
🔗 Linked issue
Resolves #4148
❓ Type of change
📚 Description
The Cloudflare dev preset (
src/presets/cloudflare/dev.ts) injects awranglerkey intoruntimeConfigat module installation time to share Miniflare configuration (config path, persist dir, environment) with the runtime plugin.However, this internal key is not filtered out during type generation in
src/build/types.ts. The existing filter only excludesappandnitro:This causes
wranglerto appear in the generatedNitroRuntimeConfiginterface (node_modules/.nitro/types/nitro-config.d.ts), which then produces a type error in the user'snitro.config.tsbecausewrangleris a required property that the user never defined.Steps to reproduce:
preset: 'cloudflare_module'nitro dev(ornitro prepare— the Cloudflare dev module runs in both)tsc --noEmitProperty 'wrangler' is missing in type '...' but required in type 'NitroRuntimeConfig'Fix: Add
wranglerto the exclusion list alongsideappandnitro.📝 Checklist