Repository navigation
Conversation
…g silent The module's deploy-safety guard only checked that worker.ts exists, while its own warning text demands it re-export ShardDO. A worker.ts that only re-exports Nitro's handler (or is unreadable) silenced the warning identically to a correct file, so a project could deploy with the SHARD Durable Object unexported and only discover it at runtime as a broken realtime plane -- the same inert-guard shape the Astro integration's cf-service check was fixed for. checkWorkerEntry mirrors that Astro precedent: exists-check, then a readFileSync in a try/catch that degrades to a warning (existsSync passing doesn't mean the file is readable), then a content check for an actual ShardDO export. Extracted into its own exported function since defineNuxtModule's setup needs full Nuxt Kit scaffolding to invoke directly, unlike Astro's plain-object integration hooks. All three outcomes (missing / unreadable / no ShardDO export) warn and never throw, matching the existing "warn rather than fail an otherwise-valid build" stance.
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
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 |
❌ Deploy Preview for lunorash failed.
|
|
Thank you for following the naming conventions! 🙏 |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
|
Closing: this PR was opened in error by an automated run, outside the scope of its task. No work is lost — the branch is retained on origin and this PR can be reopened at any time. Context: this branch predates the merges of #288 and #289, so much of its content is already on |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Branched before #288/#289 landed, so it needs a rebase onto current alpha before merge.
Commits
Files this branch still changes relative to alpha