@bcc-code/design-tokens 5.1.45 → 5.1.47
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -0
- package/build/primevue/component-dark.js +2914 -145
- package/build/primevue/component-light.js +2921 -152
- package/build/primevue/config.js +3231 -1112
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,6 +20,19 @@ For usage instructions, component guidelines, and examples, see the full documen
|
|
|
20
20
|
- [Foundations](https://developer.bcc.no/bcc-design/foundations/) - Tokens, colors, typography, spacing
|
|
21
21
|
- [Components](https://developer.bcc.no/bcc-design/components/) - PrimeVue component styling
|
|
22
22
|
|
|
23
|
+
## Adding Component Tokens
|
|
24
|
+
|
|
25
|
+
When designers add or update PrimeVue component tokens via Figma:
|
|
26
|
+
|
|
27
|
+
1. **Export from Figma** — Component tokens land in `tokens/aura/component.json`
|
|
28
|
+
2. **Add theme overrides (recommended)** — For light/dark differentiation, add the component to both `tokens/aura/component/light.json` and `tokens/aura/component/dark.json`. Without these, the component will use the same tokens in both themes.
|
|
29
|
+
3. **Run the build** — `node export-tokens/build.js`
|
|
30
|
+
4. **Check warnings** — The build will warn about components missing theme overrides
|
|
31
|
+
|
|
32
|
+
Component tokens are automatically picked up from `component.json` — no manual list to maintain.
|
|
33
|
+
|
|
34
|
+
For BCC-specific layout/sizing overrides (not from Figma), add them to `MANUAL_COMPONENT_OVERRIDES` in `export-tokens/constants.js`.
|
|
35
|
+
|
|
23
36
|
## License
|
|
24
37
|
|
|
25
38
|
MIT
|