The registry — kloq React calendar

The npm package is the compiled build. The registry is the source tier: every item is delivered by the shadcn CLI as source files copied into your project — the calendar itself, and the add-on blocks built around it. You can edit the code from the moment it lands. It is licensed per team under the Kloq Source License included in the installed files.

Point the CLI at kloq

Source access comes with a registry token — join the waitlist for yours; it arrives by email. Put it in .env.local, add the registry to components.json once, then install items by name with the @kloq namespace.

.env.local

KLOQ_REGISTRY_TOKEN=kloq_…

components.json

{
  "registries": {
    "@kloq": {
      "url": "https://kloq.dev/r/{name}.json",
      "headers": { "Authorization": "Bearer ${KLOQ_REGISTRY_TOKEN}" }
    }
  }
}

terminal

npx shadcn@latest add @kloq/kloq       # the calendar
npx shadcn@latest add @kloq/calendar   # blocks built on it

Lost the token, or want to rotate it? kloq.dev/registry/token sends a sign-in link to your purchase email; rotating mints a new token and invalidates every old one.

The catalog

Item	Type	Notes
`@kloq/kloq`	component	The calendar itself — the full library source (drag engine, views, themes, ⌘K, design mode) copied into your repo under the Kloq Source License.
`@kloq/calendar`	block	A full-page kloq calendar with the stock toolbar — the quick start as a drop-in block.
`@kloq/timeline`	block	A full-page resource timeline — rooms as lanes, `byResourceId()` as the adapter, drag to book, drag across rows to reassign. See Resource timeline.
`@kloq/utc-gutter`	component	A two-column time axis (UTC + local) for the TimeGutter slot — the slot contract in its simplest useful form.
`@kloq/zone-gutter`	component	A time axis with extra columns for any IANA zones, DST-correct against the represented day.

@kloq/kloq is the whole library — the drag engine, every view, themes, the ⌘K palette, design mode — landing under components/kloq/. The other items declare it as a registry dependency, so the CLI pulls the calendar in automatically the first time you install any block.

Why source, not a dependency

A calendar this opinionated is meant to be edited — the package puts a wall between you and the springs. Source in your repo means a custom slot is just another file, a theme tweak is a CSS edit, and nothing updates under you unless you re-run the CLI on purpose. The trade is honest: you take control, and that control is the feature.