@snovasys/design-system
v1.0.2
Published
Standalone design tokens + CSS for Snovasys UI-Kit (no Tailwind required at runtime in consumers when using built bundle)
Readme
@snovasys/design-system
Plain CSS design system extracted from snova-tailwind-uikit. Includes design tokens (CSS variables), kit utility classes, semantic wrappers, and shared utilities.
Install
npm install @snovasys/design-systemUsage
Full bundle (recommended) — single self-contained file: tokens, scrollable utilities, Tailwind-derived utilities, and all .snovasys-* rules. No @import of other package paths — safe to reference from Angular angular.json or any bundler.
<link rel="stylesheet" href="node_modules/@snovasys/design-system/dist/snovasys-design-system.css" />// angular.json styles
"styles": [
"node_modules/@snovasys/design-system/dist/snovasys-design-system.css"
]Barrel: all per-component CSS (for bundlers with CSS @import resolution, e.g. Vite or PostCSS postcss-import):
@import '@snovasys/design-system/component-imports';This pulls in tokens, utilities/_scrollable.css, and every src/components/*.css. You still need either the full bundle or your own Tailwind build for kit utility classes (bg-primary, size-5, etc.) on raw markup.
Single component
@import '@snovasys/design-system/components/button.css';Dark mode (matches UI-Kit): add class dark on <html> or a root element.
Semantic + utilities
- Use
.snovasys-{name}as a host class (see COMPONENTS.md). - Kit Tailwind utility classes used by the Angular components are included in the bundle (e.g.
bg-primary,size-24).
Publish (maintainers)
From this folder, if npm publish says ENEEDAUTH, point at the monorepo .npmrc that has your npm token:
npm run publish:npmBuild (maintainers)
From monorepo root Snovasys-New-Uikit-Library:
cd projects/snovasys-design-system
npm install
npm run buildOutputs dist/snovasys-design-system.css and dist/snovasys-design-system.min.css.
Parity check
npm run check:parityFails if a UI-Kit component folder has no matching src/components/{slug}.css.
