@bcc-code/component-library-vue 0.0.0-dev.e62c0ba → 0.0.0-dev.e994f0d

package/README.md

@@ -44,7 +44,7 @@ app.mount('#app');
 
 ### Styles Option 1 — Recommended: full Tailwind in your app
 
-Use this if you want Tailwind utility classes in your own templates and only ship the classes you use (tree-shaking).
+Use this if you want Tailwind utility classes in your own templates while still letting the library's components render correctly.
 
 1. **Add the Tailwind Vite plugin** (the package brings Tailwind in as a dependency; you only wire it up):
 
@@ -64,7 +64,12 @@ export default defineConfig({
 @import '@bcc-code/component-library-vue/theme.css';
 ```
 
-Tailwind will run as part of your build and only include the utility classes that appear in your app and in the library.
+That single import is enough. `theme.css` includes:
+
+- BCC design tokens, `@theme` / `@utility` definitions, and the rest of the design-system CSS inlined from `src/style.css` (including component-specific rules such as `BccInput` icon sizing and `BccButton` context tokens).
+- `library-utilities.css`, the pre-compiled Tailwind **utility class** rules used inside library templates (which your build cannot infer from the published JS).
+
+Do **not** rely on `library-utilities.css` alone with a minimal “base” import: you still need the full `theme.css` (or `style.css` for Option 2) so non-utility component styles and tokens are present. 
 
 ### Styles Option 2 — Pre-built CSS only