How it works

Most UI libraries are packages: you install them, import from node_modules, and wait for the maintainers when you need something changed. tealmac UI works the other way round.

A registry, not a package

The library is published as a shadcn registry: a set of JSON files, one per item, each holding the item's source files, the npm packages it needs and the other registry items it builds on. The shadcn CLI reads that JSON and writes the files into your project.

pnpmnpmyarnbun
pnpm dlx shadcn@latest add https://ui.tealmac.com/r/marquee.json
Copy

After that command, components/ui/marquee.tsx is a normal file in your repository. Nothing at runtime refers back to us.

You own the code

Because the source lives in your project:

• You can change anything. Markup, timing, colours, props. There is no API surface to work around and no styles to override.
• Your bundle only has what you use. There is no library entry point that pulls in components you never render.
• Nothing breaks on its own. A new release can't change your app until you choose to pull it in.

What an item contains

Shared pieces such as cn() in lib/utils.ts and the shadcn/ui primitives are declared as dependencies, so the CLI adds them once and reuses them.

Updates

Owning the code means updates are your call. When a component improves, the changelog says so, and you can compare or reinstall it. The update guide shows how to pull a new version without losing your edits.

Free and Pro

Every component is MIT licensed. Pro templates and blocks use the same registry format, served from a licence-checked address. See Set up Pro.