Skip to content
DocsSupportPricing
Roadmap (has updates coming soon)XFigma3.7K
Sign inGet All-Access
Overview
  • Introduction
  • Get Started
  • License Setup
  • Styling
  • Registry
  • MCP Server
  • Embed
  • Agent Skills
  • llms.txt
  • RTL
  • Changelogv2.8.1
  • YouTube
MCP Server
  • Claude
  • CodexCodexCodex
  • Cursor
  • Grok
  • Conductor
  • v0
  • Lovable
  • Replit
  • Bolt
  • OpenCode
  • VS Code
  • GitHub Copilot
  • Kilo Code
  • Zed
  • Antigravity
  • Gemini CLI
Components
  • Alert
  • Autocomplete
  • Badge
  • CascaderCascader keeps a saved selection's full path, popup open or closed
  • Code Block
  • Color Picker
  • Data GridData Grid works in apps that run React Compiler, with resizing, edits and callbacks kept live
  • Date SelectorDate Selector keeps its year list and Today button current in apps that run React Compiler
  • Emoji Picker
  • Event CalendarEvent Calendar keeps today and the agenda current in apps that run React Compiler
  • File TypeFile Type knows 171 formats, .env and Dockerfile included
  • File Upload
  • Filters
  • Frame
  • GanttGantt keeps its Today button and tooltip current in apps that run React Compiler
  • Icon Stack
  • Icon Tile
  • Kanban
  • Number Field
  • Phone Input
  • Rating
  • Scrollspy
  • Signature Pad
  • Sortable
  • Stepper
  • Time Picker
  • Timeline
  • Tree

License Setup

PreviousNext

Configure your ReUI license key for premium registry installs.

Use this guide when you want to install premium ReUI registry items with the shadcn CLI. Free components do not require a license key, but premium blocks and icons do. Templates are not registry items: download each one from its page in Templates.

Your License Key

Use the license key from your ReUI account:

You need to be logged in to see your license key

Login

CLI Installation

This is the recommended setup for premium registry installs.

Prerequisites

  • A React project with shadcn/ui initialized
  • Node.js 18 or newer
  • A components.json file in your project root

Add your license key

Put it in .env.local in the root of your project:

REUI_LICENSE_KEY=your-license-key-here

Point components.json at the @reui registry

Update components.json to use the authenticated @reui registry config:

{
  "registries": {
    "@reui": {
      "url": "https://reui.io/r/{style}/{name}.json",
      "headers": {
        "Authorization": "Bearer ${REUI_LICENSE_KEY}"
      }
    }
  }
}

The shadcn CLI expands ${REUI_LICENSE_KEY} from your environment, so leave it as a variable here. A ReUI MCP server entry is a separate config with its own rules, and they differ by client: Claude Code expands ${VAR} in .mcp.json, Cursor and VS Code only understand the env: prefix (${env:NAME}, and VS Code also takes an ${input:...} prompt), OpenCode uses single braces with no dollar sign ({env:NAME}), Codex reads the value from bearer_token_env_var, and Antigravity's mcp_config.json documents no substitution at all, so there the real token gets pasted in. Check your agent's guide before copying this line across, and create a token at Account → MCP.

Install registry items

Install from the same namespace:

pnpm dlx shadcn@latest add @reui/c-data-grid-1

Free components continue to work with the authenticated config, so you do not need a second registry namespace.

Monorepo (Turborepo)

Installing into a shared package such as packages/ui works the same way, with three things to get right. All three follow from one rule: the CLI reads components.json and .env.local from the directory it runs in, and looks nowhere else.

Put components.json in the package, not the repo root

Every workspace needs its own components.json, and the @reui registry block belongs in the one you install from:

packages/ui/components.json
{
  "aliases": {
    "components": "@workspace/ui/components",
    "ui": "@workspace/ui/components",
    "lib": "@workspace/ui/lib",
    "hooks": "@workspace/ui/hooks",
    "utils": "@workspace/ui/lib/utils"
  },
  "registries": {
    "@reui": {
      "url": "https://reui.io/r/{style}/{name}.json",
      "headers": {
        "Authorization": "Bearer ${REUI_LICENSE_KEY}"
      }
    }
  }
}

The aliases are what land the files in packages/ui instead of in an app.

Keep the key next to it

The CLI loads .env.local from the directory it runs in and does not walk up to parent folders, so a key kept only in the repo root's .env.local is never seen. That is the Registry "@reui" requires the following environment variables error, and it stops before any request is made:

packages/ui/.env.local
REUI_LICENSE_KEY=your-license-key-here

Run the install from the package

cd packages/ui
npx shadcn@latest add @reui/c-data-grid-1

Or stay at the repo root and point the CLI at the package, which is what it suggests itself when run from there:

pnpm dlx shadcn@latest add -c packages/ui @reui/c-data-grid-1

Running from a directory whose components.json has no @reui block (the root, or an app) is the other way this fails: the CLI falls back to shadcn's public directory entry for @reui, which carries no license header, so reui.io answers You are not authorized to access the item even though the key is set.

Consuming apps then import as usual, and need no license key of their own:

import { DataGrid } from "@workspace/ui/components/reui/data-grid/data-grid"

Prefer shadcn's own monorepo layout, where installs run from apps/web? That works too: put the same registries block and .env.local in apps/web instead. The ui alias still lands the files in packages/ui.

Passing the key from your shell or CI environment instead of the env file, through a turbo task? Turborepo 2 defaults to strict environment mode, which hands a task only the variables declared in turbo.json, so add REUI_LICENSE_KEY to globalEnv there. With the key in packages/ui/.env.local this does not apply: the CLI reads that file itself, inside the task.

Manual Copy & Paste

Prefer to browse and copy code directly instead of using the CLI?

  • Browse premium sections in Blocks
  • Browse premium icon packs in Icons
  • See plan details in Pricing

Related Guides

  • Get Started
  • Registry
Get StartedStyling

On This Page

Your License KeyCLI InstallationPrerequisitesMonorepo (Turborepo)Manual Copy & PasteRelated Guides

Application

  • App Shell
  • Auth
  • Card
  • Dashboard
  • Dialog
  • Empty State
  • Event Calendar
  • Flow
  • Form
  • Gantt
  • Kanban Board
  • List
  • Navbar
  • Onboarding
  • Profile
  • Rich Text Editor
  • Schedule
  • Settings
  • Sheet
  • Stats2 meter cards moved here from Charts, 17 in all
  • Timeline
  • Whiteboard
  • Wizard

Data Grid

  • Base
  • AdvancedAdded 2 new Data Grid Advanced blocks, 5 in all
  • Columns
  • Drag & Drop
  • Editing
  • Expansion
  • Filtering
  • Grouping
  • Virtualization

Charts

  • Area ChartAdded a new Inbound Leads area chart block
  • Bar Chart
  • Composed Chart
  • Line Chart
  • Pie Chart
  • Radial Chart
  • Sankey ChartNew Sankey Chart category with 3 flow chart blocks
  • Slope ChartNew Slope Chart category with 2 rank-shift chart blocks
  • Sparkline
  • Status Tracker

AI & Agents

  • AI Chat
  • Agent Activity
  • AI UsageNew AI Usage category with 2 spend blocks

Solutions

  • Dev Ops
  • AI Ops
  • CRM
  • Agents
  • Analytics
  • Billing
  • Bookings
  • Files
  • Inventory
  • Users
  • Digital TwinNew Digital Twin category with 2 interactive 3D blocks

Templates

  • All templates

eCommerce

  • Category Card
  • Checkout
  • Comparison
  • Coupon
  • Filter Sidebar
  • Product Card
  • Product Detail
  • Product Grid
  • Receipt
  • Review
  • Shopping Cart
  • Wishlist
  • Shop Hero

Marketing

  • Blog
  • Compare
  • Contact
  • CTA
  • FAQ
  • Hero
  • How It Works
  • Pricing

Resources

  • Components
  • Blocks
  • Icons
  • MCP for Agents
  • Docs
  • Support
  • Pricing
  • Tailwind Plus Alternative
  • Roadmap(has updates coming soon)
  • AffiliateSoon

Legal

  • Privacy Policy
  • Terms & Conditions
  • License
  • Refunds
  • Cookies

© 2026 ReUI. All rights reserved.

3.7K