C3 - Capacity Core Components

Installation

git clone https://gitlab.aisoftware.com/frontend/c3.git
cd c3
npm install

Running Storybook

npm run storybook

Running the "Playground"

npm run dev

Build Library

npm run build

Releasing

Publishing is automated. .github/workflows/publish.yml runs on every push to main and publishes to npm whenever the version in package.json isn't already there. There is no separate release step, so the version bump has to land in the feature PR itself. If you forget it, nothing fails — the workflow just logs "already published" and ships nothing.

Before committing a change that affects consumers of dist/:

npm run release

That runs changeset (prompts for the bump type and a summary), then changeset version — which bumps package.json, prepends your summary to CHANGELOG.md, and deletes the consumed changeset file — then npm install --package-lock-only to sync the lockfile, which changeset version doesn't touch on its own.

Commit all three files — package.json, package-lock.json, and CHANGELOG.md — alongside your code. Changesets is configured with commit: false and won't commit for you.

Bump types: patch for fixes with no API change, minor for new components/props or intentional visual changes, major for breaking API removals.

Changes that never reach dist/ — CI config, README, stories-only edits — don't need a changeset.