Skip to content

fix(nuxt): verify worker.ts actually re-exports ShardDO before staying silent - #307

Closed
prisis wants to merge 1 commit into
alphafrom
advisor/281-nuxt-worker-guard
Closed

prisis wants to merge 1 commit into
alphafrom
advisor/281-nuxt-worker-guard

Conversation

@prisis

@prisis prisis commented Aug 2, 2026

Copy link
Copy Markdown
Member

Branched before #288/#289 landed, so it needs a rebase onto current alpha before merge.

Commits

  • fix(nuxt): verify worker.ts actually re-exports ShardDO before staying silent

Files this branch still changes relative to alpha

packages/nuxt/__tests__/module-worker-guard.test.ts
packages/nuxt/src/module.ts

…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.
@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@prisis, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: fb644090-753e-44cc-9486-19ca00c8bf15

📥 Commits

Reviewing files that changed from the base of the PR and between 6a4dd72 and 6a64f83.

⛔ Files ignored due to path filters (1)
  • packages/nuxt/__tests__/module-worker-guard.test.ts is excluded by !**/__tests__/**, !**/*.test.ts and included by packages/**
📒 Files selected for processing (1)
  • packages/nuxt/src/module.ts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@netlify

netlify Bot commented Aug 2, 2026 •

Copy link
Copy Markdown

❌ Deploy Preview for lunorash failed.

Name Link
🔨 Latest commit 6a64f83
🔍 Latest deploy log https://app.netlify.com/projects/lunorash/deploys/6a6f0b6b6d8d08000811e1e5

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Thank you for following the naming conventions! 🙏

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Thank you for confirming the Contributor License Agreement! 🙏

@prisis

prisis commented Aug 2, 2026

Copy link
Copy Markdown
Member Author

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 alpha, and it would need a rebase before being reviewable. Reopening deliberately, after a rebase, is preferable to leaving it open in this state.

@prisis prisis closed this Aug 2, 2026
@prisis
prisis deleted the advisor/281-nuxt-worker-guard branch August 2, 2026 09:57
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

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.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Sep 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant