rwsdk-shadcn-update

To safely update shadcn/ui components in RedwoodSDK, run a structured workflow that analyzes your project, backs up custom components, updates via CLI or MCP, restores customizations, and validates with type checks and builds.

You can identify custom shadcn components by running a Phase 1 project-specific analysis, which automatically detects fully custom and modified components to prevent overwriting customizations during updates.

Yes, the shadcn update workflow ensures React Server Components (RSC) compliance by fetching the latest RedwoodSDK guidance and validating components across your project to maintain compatibility.

The best way to add new shadcn components without breaking customizations is to use a safe update workflow that backs up modified files, applies the update, restores your custom code, and runs build validation.

Yes, you can use optional MCP server integration to manage shadcn components, allowing you to execute updates and maintain project health alongside standard pnpm, yarn, or npm package managers.

Shadcn components break after updating in RedwoodSDK when custom modifications are overwritten without backups; applying a structured workflow that backs up, updates, restores, and validates prevents these rendering issues.