fix: nitro v3 plugin link in the hosting docs

[gtg7784]

The nitro v3 plugin link is incorrect, fix with correct one

Summary by CodeRabbit

• Documentation
  • Updated Vercel deployment guide to reference the correct Nitro v3 Vite plugin (now nitro-nightly), keeping the BETA status note.
  • Clarifies deployment steps for React users relying on Nitro v3, reducing confusion from outdated plugin naming.
  • Ensures alignment with current tooling to improve setup reliability and developer confidence.

[coderabbitai]

Walkthrough

Updated documentation for React hosting: in the Vercel deployment guide, the Nitro v3 Vite plugin reference was changed from nitro-vite to nitro-nightly. No other content changes reported.

Changes

Cohort / File(s)	Summary of Changes
Docs: React Hosting (Vercel) docs/start/framework/react/hosting.md	Replaced Nitro v3 Vite plugin name from nitro-vite to nitro-nightly; description unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

documentation

Poem

Hop-hop! I tweak, I cite,
Turn nitro-vite to nightly light.
Docs now shine in lunar glow,
Vercel routes are good to go.
Little paws, precise and spry—
Ship the words, then nuzzle by. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly and concisely describes the primary change—updating the Nitro v3 plugin link in the hosting documentation—without unnecessary detail or ambiguity. It directly reflects the PR’s scope, allowing reviewers to understand its purpose at a glance. This alignment with the main change ensures clarity in the project’s history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0babe5d and cc2f814.

📒 Files selected for processing (1)

• docs/start/framework/react/hosting.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (AGENTS.md)

Use internal docs links relative to the docs/ folder (e.g., ./guide/data-loading)

Files:

• docs/start/framework/react/hosting.md

docs/{router,start}/**

📄 CodeRabbit inference engine (AGENTS.md)

Place router docs under docs/router/ and start framework docs under docs/start/

Files:

• docs/start/framework/react/hosting.md

🔇 Additional comments (1)

docs/start/framework/react/hosting.md (1)

122-122: Correct link now matches install instructions

Thanks for updating the Nitro v3 plugin link to nitro-nightly; this aligns with the installation guidance later in the doc where we pin "nitro": "npm:nitro-nightly". Looks good.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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 and usage tips.}