Fix: Preserve 'use client' directive in universal registry items

[VeiaG]

Fixes #8432

Problem

Universal registry items (registry:file and registry:item) are designed to be framework-agnostic components that can be installed without running shadcn init or having a components.json file. These items should preserve their original content as-is.

However, the transformRsc transformer was incorrectly removing 'use client' directives from universal item files when config.rsc was false or undefined. This broke client-side functionality in universal items that require React hooks or browser APIs.

Why this happens:

1. Universal items can be installed without project setup
2. When no config exists or rsc is false by default, the RSC transformer runs
3. The transformer removes 'use client' from ALL files, including universal items
4. This breaks the original functionality of universal items

Solution

Skip all transformers for universal registry items (registry:file and registry:item types) to preserve their original content, similar to how .env files are handled.

Universal items are meant to be copied exactly as-is from the registry, so they should bypass:

• RSC transformer
• Import transformer
• CSS variables transformer
• Tailwind prefix transformer
• Icon transformer
• Next.js middleware transformer

Regular shadcn components (registry:ui, registry:lib, etc.) continue to have transformers applied as expected.

Changes

Modified Files

packages/shadcn/src/utils/updaters/update-files.ts

• Added check to identify universal item files before applying transformers
• Skip all transformers for registry:file and registry:item types
• Preserve original content including 'use client' directives

packages/shadcn/test/utils/updaters/update-files.test.ts

• Added test: verify 'use client' is preserved in registry:file items
• Added test: verify 'use client' is preserved in registry:item items
• Added test: verify 'use client' is still removed from regular components when rsc: false

Testing

The fix includes comprehensive tests to ensure:

1. ✅ Universal items (registry:file) preserve 'use client' directives
2. ✅ Universal items (registry:item) preserve 'use client' directives
3. ✅ Regular components still have transformers applied correctly
4. ✅ Existing functionality for non-universal items remains unchanged

Impact

• Universal items: Now work correctly without project initialization
• Regular components: No change in behavior
• Backward compatibility: Fully maintained

This ensures universal items work as intended - as standalone, framework-agnostic components that can be copied and used immediately without any transformations.

[vercel]

@VeiaG is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.

[VeiaG]

Gentle ping — let me know if I can do anything to help move this PR forward )