feat: add rsbuild docs

[Nsttt]

What's added in this PR?

Add rsbuild docs for rsbuild plugin. Related ZephyrCloudIO/zephyr-packages#197

(Required) Pre-PR/Merge checklist

• I have added/updated our feature to sync with this PR
• I have added an explanation of my changes
• I have/will run tests, or ask for help to add test

[claude]

Claude finished @Nsttt's task —— View job

---

Comprehensive PR Review

Note: Writing @claude please review in a comment will trigger a full review.

Todo List:

• Get PR diff information to understand exact changes and line numbers
• Analyze the new Rsbuild documentation file
• Review configuration changes for correctness and security
• Check for coding standards, performance, and maintainability issues
• Provide structured feedback with severity table
• Give overall quality score and recommendations

---

Purpose Summary: This PR adds comprehensive Rsbuild integration documentation for Zephyr Cloud, including setup instructions, Module Federation support, and configuration examples.

Review Findings

Issues and Recommendations

Severity	File/Line(s)	Issue	Recommendation
Medium	docs/recipes/react-rsbuild.mdx:6-12	Unused imports	Remove unused imports: SupportedBrowser, DrawingPinIcon, Image, Keyboard, SourceCode, Tabs, TabsContent, TabsList, TabsTrigger, Card
Medium	docs/recipes/react-rsbuild.mdx:114	Hardcoded localhost URL	Replace http://localhost:3001/remoteEntry.js with environment variable or placeholder
Low	docs/recipes/react-rsbuild.mdx:139	Inconsistent option naming	Use camelCase waitForIndexHtml instead of snake_case wait_for_index_html
Low	lib/site.config.tsx:415-417	Missing icon configuration	Add appropriate icon for Rsbuild bundler entry (currently empty string)
Low	docs/recipes/react-rsbuild.mdx:159	Missing trailing newline	Add trailing newline at end of file

Code Quality Assessment

Strengths:

• ✅ Well-structured documentation following existing patterns
• ✅ Comprehensive coverage including basic setup, Module Federation, and troubleshooting
• ✅ Consistent with other recipe documentation in the codebase
• ✅ Good use of code blocks with proper language tags
• ✅ Appropriate use of MDX components and styling
• ✅ Clear step-by-step instructions

Areas for Improvement:

1. Import Cleanup: The documentation imports several UI components that are never used, adding unnecessary bundle size.

// Remove these unused imports:
import SupportedBrowser from "../../components/browser-table";
import { DrawingPinIcon } from '@radix-ui/react-icons';
import { Image } from "../../components/ui/image";
import { Keyboard } from "../../components/ui/keyboard";
import { SourceCode } from '@theme';
import { Tabs, TabsContent, TabsList, TabsTrigger } from "../../components/ui/tabs";
import { Card } from "../../components/ui/card";

2. Configuration Consistency: The Module Federation example uses a hardcoded localhost URL which isn't suitable for production documentation.

// Current:
remotes: {
  remote: 'remote@http://localhost:3001/remoteEntry.js',
},

// Better:
remotes: {
  remote: 'remote@https://your-remote-app.com/remoteEntry.js',
  // or use environment variable example
  remote: `remote@${process.env.REMOTE_URL}/remoteEntry.js`,
},

3. API Consistency: The advanced configuration example uses snake_case which is inconsistent with JavaScript conventions.

// Current:
withZephyr({
  wait_for_index_html: true,
})

// Better:
withZephyr({
  waitForIndexHtml: true,
})

Security Review

• ✅ No security vulnerabilities identified
• ✅ No hardcoded secrets or sensitive information
• ✅ External links are appropriate and safe
• ✅ No XSS or injection vectors in the documentation

Performance Considerations

• ✅ Documentation structure is efficient
• ⚠️ Unused imports slightly increase bundle size (minor impact)
• ✅ Code examples follow performance best practices

Test Coverage

• ℹ️ Documentation files typically don't require unit tests
• ✅ Configuration examples are syntactically correct
• ✅ Links and references appear valid

Overall Quality Score: 8.5/10

This is a high-quality addition to the documentation that follows established patterns and provides comprehensive guidance for Rsbuild integration. The documentation is well-structured, clear, and includes all necessary setup steps.

Top 3 Next Steps:

1. Clean up unused imports - Remove the 7 unused import statements to reduce bundle size
2. Fix configuration examples - Replace hardcoded localhost URL with a more appropriate example and use camelCase for option naming
3. Add Rsbuild icon - Complete the bundler configuration by adding an appropriate icon for the Rsbuild entry

The PR is ready for merge after addressing these minor cleanup items. The core functionality and documentation quality are excellent.

---