Package structure
TL;DR If you're new to the @getsoren/design-system repository, here's what each top-level piece is for.
Folders#
Path
What it's for
src/The library source — the components published as @getsoren/design-system.
colors/Source for the standalone colors sub-package. See colors package .
.storybook/Storybook configuration for the visual component catalog. See Storybook .
.github/GitHub configuration, including CI workflows.
.husky/Git hooks, run via Husky. See tech stack .
Config files#
File
What it's for
package.jsonPackage metadata and scripts (dev, build, preview, storybook).
vite.config.tsVite build and dev server configuration.
test.config.tsVitest test configuration. See testing .
tsconfig.json / tsconfig.node.jsonTypeScript configuration.
biome.jsonBiome linter/formatter configuration.
Dockerfile / docker-compose.ymlDocker setup for running Storybook without a local Node install.
bun.lockLockfile for bun installs.
How the package is published#
Consumers install the whole package with npm install @getsoren/design-system (or bun/yarn/pnpm — see installation ), and can reach sub-packages like colors at @getsoren/design-system/colors.
← Back: Tech stack · Next: About Soren →
