docs: clarify Firebase Cloud Functions coexistence

[Ibochkarev]

🔗 Linked issue

Refs #1497

📚 Description

The Firebase deploy page only showed firebase deploy --only, so it sounded like other Cloud Functions could not live next to Nuxt. Firebase already supports multiple function sources with codebase.

I updated the Other Cloud Functions section with a multi-source firebase.json example, a link to Firebase's monorepo docs, and --only examples for both the nuxt codebase and a single-source setup.

[vercel]

@Ibochkarev is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 19 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4db48913-ad12-419c-86d9-1f8e5e3a6bca

📥 Commits

Reviewing files that changed from the base of the PR and between d41604b and 483509d.

📒 Files selected for processing (1)

• content/deploy/firebase.md

📝 Walkthrough

Walkthrough

Updated Firebase deployment guidance for Nuxt applications. The documentation covers coexistence with other Cloud Functions, separate function sources with distinct codebase values, deployment of the nuxt codebase with hosting, and targeting functions:server when using one source.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the documentation change about Firebase Cloud Functions coexistence.
Description check	✅ Passed	The description directly explains the Firebase documentation updates and matches the changeset objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@content/deploy/firebase.md`:
- Around line 167-169: Update the Firebase deployment guidance around the single
`functions` configuration entry to explain that deletion warnings depend on
shared `codebase` identifiers, not source count alone. Clarify that a single
source with a unique codebase can coexist with other functions, then document
the multi-source configuration and require distinct codebase values across
separate repository configurations.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 25290dff-0a7b-4bae-8ed0-9fbe72b2cab8

📥 Commits

Reviewing files that changed from the base of the PR and between 29e59bb and d41604b.

📒 Files selected for processing (1)

• content/deploy/firebase.md