@boostdev/design-system-components 0.1.2 → 0.1.3

package/AGENTS.md

@@ -39,9 +39,12 @@ Or individual token layers. All component styles live inside `@layer component`.
 ## Import paths
 
 ```ts
-// Named exports from the main barrel
+// Named exports — plain React / Vite
 import { Button, Badge, Typography } from '@boostdev/components';
 
+// Named exports — Next.js / RSC (adds 'use client' to the bundle)
+import { Button, Badge, Typography } from '@boostdev/components/client';
+
 // CSS (import once, at the app root)
 import '@boostdev/components/css';
 ```

package/README.md

@@ -37,6 +37,25 @@ cascade. You can override any component from outside without specificity fights.
 
 ---
 
+## Next.js / React Server Components
+
+The main `@boostdev/components` entry has no `'use client'` directive. When Next.js evaluates the
+bundle in a React Server Component context, components that call `createContext` (e.g. `Toast`) will
+crash at module evaluation time.
+
+Use the `/client` subpath instead — it is identical in API but has `'use client'` prepended to the
+bundle, which tells Next.js to treat it as client-only code:
+
+```ts
+// Plain React / Vite — unchanged
+import { Button, Card } from '@boostdev/components';
+
+// Next.js / RSC — use the /client subpath
+import { Button, Card } from '@boostdev/components/client';
+```
+
+---
+
 ## Usage
 
 ### UI components