Update static plugin configuration for React docs

[sancho1952007]

The 'bunFullstack' parameter wasn't present in the docs causing the browser to throw issue parsing React code.

I've added the bunFullstack parameter to the docs so that React can be rendered properly.

Without this parameter, React doesn't render at all but instead throws an error in the browser console.

Summary by CodeRabbit

• Documentation
  • Updated Fullstack Dev Server documentation with clearer React configuration guidance. Added explicit instructions for required settings to enable React support in Bun's development environment, including configuration examples for both standard and custom file serving paths.

[coderabbitai]

Walkthrough

Documentation updates clarify that bunFullstack: true must be set in staticPlugin configuration for React support. A tip block was added, and both the initial setup and custom prefix path examples now include this required parameter.

Changes

React Configuration Documentation for Fullstack Dev Server

Layer / File(s)	Summary
React requirement tip and configuration examples docs/patterns/fullstack-dev-server.md	Inserts a tip documenting the bunFullstack: true requirement for React, then updates the initial staticPlugin setup example and the custom prefix path example to include bunFullstack: true in their configurations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

✨ A tiny doccc update so you don't mess up React's setup~~
bunFullstack: true—duh, it's not that hard, baka~ (´；ω；`)
Multiple examples to show you how it's done (๑•́ ω •̀)و ♡
Even added a tip so you can't complain~~ ✌︎('ω') ✌︎

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the static plugin configuration in React documentation by adding the bunFullstack parameter.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

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

[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 `@docs/patterns/fullstack-dev-server.md`:
- Line 126: The example contains an invalid TypeScript token "bunFullstack: true
[!code++]" which will break copy-paste; edit the snippet that includes the
"bunFullstack: true [!code++]" line to remove the stray "[!code++]" token or
replace it with a valid code-highlight/comment marker appropriate for TypeScript
examples (so the line reads a valid TS assignment like "bunFullstack: true" or
the same plus a proper inline comment), and ensure any surrounding code block
metadata uses the docs' supported syntax for highlighting rather than inserting
that token into the code.

🪄 Autofix (Beta)

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

Run ID: 69b8e84b-29a8-4fa6-a5ea-402f7f04b5f1

📥 Commits

Reviewing files that changed from the base of the PR and between b8eced1 and 5d8c156.

📒 Files selected for processing (1)

• docs/patterns/fullstack-dev-server.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Custom prefix example contains invalid TypeScript token ([!code++])

Heh, this snippet will blow up if someone copy-pastes it, genius~ bunFullstack: true [!code++] is not valid TS and breaks the docs example UX. Use a proper code-highlight comment marker instead (or remove it). (￣ω￣;)

Suggested fix

-			bunFullstack: true [!code++]
+			bunFullstack: true // [!code ++]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	bunFullstack: true [!code++]
	bunFullstack: true // [!code ++]

🤖 Prompt for 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.

In `@docs/patterns/fullstack-dev-server.md` at line 126, The example contains an
invalid TypeScript token "bunFullstack: true [!code++]" which will break
copy-paste; edit the snippet that includes the "bunFullstack: true [!code++]"
line to remove the stray "[!code++]" token or replace it with a valid
code-highlight/comment marker appropriate for TypeScript examples (so the line
reads a valid TS assignment like "bunFullstack: true" or the same plus a proper
inline comment), and ensure any surrounding code block metadata uses the docs'
supported syntax for highlighting rather than inserting that token into the
code.