feat: add nuxt-endpoints module - #1585
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan includes up to 4 reviews per rolling hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe change adds the Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This PR adds the module’s registry metadata and icon without any identified merge-blocking risk; it is merge-ready after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
61e4b4f to
3a017bf
Compare
🔗 Linked issue
nuxt-endpoints#1584📚 Description
This PR adds nuxt-endpoints to the Nuxt modules registry.
nuxt-endpoints brings RPC-like end-to-end type safety to native Nuxt server routes without replacing Nuxt’s file-based routing. Users define a contract alongside each handler with Zod, Valibot, or Effect Schema, and the module derives:
This preserves HTTP methods, status codes, and OpenAPI interoperability while avoiding duplicated request and response types or manually maintained Query keys. Idempotency support is also available for mutation endpoints.
Nuxt Endpoints is designed to adopt Nuxt 5 typed-fetch and stable H3/Nitro metadata primitives as they become available, while keeping executable contracts, status-aware results, runtime validation, and optional client adapters at the module layer.
The metadata was synced against the published nuxt-endpoints@0.2.0 package, and the registry build completed successfully.