Skip to content
Template Empire / components

Search components

10 results

Browse components

Own the installed source

Registry

Learn how the public @te shadcn registry resolves component source, dependencies and shared files for React and Next.js projects.

How the registry works

The @te registry follows the shadcn registry format. Each item describes its source files, runtime packages, shared registry dependencies and supported CSS variables.

Installing an item copies readable source into your project. There is no runtime Template Empire client, account check or hidden package between your application and the component.

Configure the namespace

Declare the namespace in components.json so every component can be installed with the same short command.

{
  "registries": {
    "@te": "https://templateempire.io/r/{name}.json"
  }
}

Use item URLs directly

Registry clients that do not use namespaces can request an item JSON document directly. Replace the example slug with the component you need.

https://templateempire.io/r/bg-aurora.json

Review updates intentionally

Because the source lives in your repository, local edits belong to you. Review the diff before reinstalling an updated item so upstream improvements do not overwrite deliberate product changes.

Every published item is built from the public catalogue and validated through a clean installation in CI. The component page documents its current API and dependencies.