Bitblue ships as several npm packages. Pick the umbrella if you want everything, or install only the segments your app needs.
Requirements
Peer dependencies for every package:
svelte^5tailwindcss^4@sveltejs/kit^2(when using Kit apps)
Quick start (umbrella)
Install the full library surface in one step:
pnpm add @cailabs/components
# or: npm i @cailabs/components
# or: yarn add @cailabs/components <script>
import { Button, Modal, Input } from '@cailabs/components';
</script>
<Button>Save</Button> @cailabs/components re-exports @cailabs/components.base (UI + forms + data helpers, etc.).
Install by segment
Prefer this when you only need part of the library.
| Package | Use for | What’s included |
|---|---|---|
@cailabs/components.base | Core UI | Accordion, Alert, Avatar, Badge, Button, Card, Drawer, Dropdown, Modal, Tabs, Toast, Toolbar, Tooltip, Theme, … |
@cailabs/components.forms | Forms | Input, Label, Select, Checkbox, Radio, Toggle, Datepicker, File upload, Felte-backed Form* fields |
@cailabs/components.data | Data | Table, Datatable, Paginate, TableLoader, filter builder |
@cailabs/components.layout | Layout | TF shell, Chat, mailing, ComponentCanvas + tf-layout.css |
@cailabs/components.editor | Editor | Rich-text / ClEditor integrations |
@cailabs/components.reporting | Reporting | Reporting / chart-related exports (builds on data) |
Base (UI primitives)
pnpm add @cailabs/components.base <script>
import { Button, Accordion, AccordionItem } from '@cailabs/components.base';
</script> Forms
pnpm add @cailabs/components.forms Peers you should also have (or let your package manager prompt):
pnpm add felte filepond <script>
import { Input, Label, Form, FormInput } from '@cailabs/components.forms';
</script> You can also reach the same forms barrel from base:
import { Input } from '@cailabs/components.base/forms'; Data
pnpm add @cailabs/components.data pnpm add svelte-headless-table <script>
import { Table, DataTable } from '@cailabs/components.data';
</script> Subpath alternative:
import { Table } from '@cailabs/components.base/data'; Layout
pnpm add @cailabs/components.layout <script>
import { TFLayoutWrapper } from '@cailabs/components.layout';
</script> TF layout CSS (pick one):
import '@cailabs/components.layout/tf-layout.css';
// or
import '@cailabs/components.base/tf-layout.css'; Editor
pnpm add @cailabs/components.editor Typical peers:
pnpm add @tiptap/core @tiptap/starter-kit cl-editor <script>
import { BaseEditor } from '@cailabs/components.editor';
</script> Reporting
pnpm add @cailabs/components.reporting pnpm add echarts @cailabs/components.data import { /* reporting exports */ } from '@cailabs/components.reporting'; Recommended combos
Docs / marketing UI only
pnpm add @cailabs/components.base Admin app with forms
pnpm add @cailabs/components.base @cailabs/components.forms felte Dashboard with tables + TF shell
pnpm add @cailabs/components.base @cailabs/components.data @cailabs/components.layout svelte-headless-table Tailwind v4
Point Tailwind at the package sources so utility classes used inside components are generated. In your app CSS:
@import 'tailwindcss';
@source "../node_modules/@cailabs/components.base/dist"; If you install segment packages that ship their own files, add matching @source lines for those packages as well.
Theme
Wrap your app (or a subtree) when you want token overrides:
<script>
import { ThemeProvider, Button } from '@cailabs/components.base';
</script>
<ThemeProvider>
<Button>Themed</Button>
</ThemeProvider> See Theme for the full API.
Which import path should I use?
| Goal | Use |
|---|---|
| One dependency, full API | @cailabs/components |
| UI only | @cailabs/components.base |
| Forms-focused installs | @cailabs/components.forms |
| Tables / filters | @cailabs/components.data |
| App shell | @cailabs/components.layout |
| Stay on base but import a slice | @cailabs/components.base/forms, /data, /layout, /editor, /reporting |
Segment packages are the supported install surface for apps that want clearer dependency intent. Deep per-component packages (for example @cailabs/components.button) are not published.