Installation

Set up BlakeUI Pro in your project.

Requirements

  • React 19+
  • Tailwind CSS v4
  • BlakeUI OSS (@blakeui/react + @blakeui/styles)

If you haven't set up BlakeUI OSS yet, follow the BlakeUI Quick Start first.

Login

Run the BlakeUI Pro CLI and log in with your GitHub account:

npx @blakeui/pro@latest login

A browser tab will open automatically. Sign in with your GitHub account, authorize the application, and wait for the terminal to confirm:

Logged in as @your-username

Install

Once logged in, run:

npx @blakeui/pro@latest install

The CLI configures your project and installs the packages:

  • Writes an .npmrc that points the @blakeui scope at the private registry and authenticates with your token — referenced from an environment variable, so no secret is written into the file (it's safe to commit)
  • Installs @blakeui/pro-react from the private registry with your detected package manager
  • Detects missing peer dependencies and installs them with the correct version ranges

You'll see an interactive prompt to confirm which peer dependencies to install. Press Enter to install all of them.

Import Styles

Add BlakeUI Pro styles to your main CSS file (e.g. globals.css):

globals.css
@import "tailwindcss";
@import "@blakeui/styles";
@import "@blakeui/pro-react/css";

Import order matters. Always import tailwindcss first, then @blakeui/styles, then @blakeui/pro-react/css.

Use a Pro Component

import { OrdersTable } from "@blakeui/pro-react";

function App() {
  // Renders a built-in sample dataset out of the box — pass `orders` for your own data.
  return <OrdersTable />;
}

CLI Reference

CommandDescription
blakeui-pro loginLog in with GitHub
blakeui-pro installInstall Pro packages, peer deps, and configure your PM
blakeui-pro install --yesNon-interactive install (auto-accept all prompts)
blakeui-pro install --dry-runPreview what would be installed without executing
blakeui-pro statusShow login and installed package info
blakeui-pro logoutSign out

CI/CD

For automated environments (GitHub Actions, Vercel, Netlify, etc.), use a CI/CD token instead of interactive login — no blakeui-pro login needed.

Commit the .npmrc (it references the token by name, so it carries no secret):

.npmrc
@blakeui:registry=https://registry.blakeui.pro
//registry.blakeui.pro/:_authToken=${BLAKEUI_AUTH_TOKEN}

Then expose BLAKEUI_AUTH_TOKEN to the install step:

.github/workflows/deploy.yml
env:
  BLAKEUI_AUTH_TOKEN: ${{ secrets.BLAKEUI_AUTH_TOKEN }}

Your normal install (npm ci, pnpm install, yarn, …) then resolves @blakeui/pro-* from the private registry using the token. Works with all package managers.

Use your CI/CD token for pipelines, not your personal token. CI/CD tokens are scoped to your license and can be rotated independently from Dashboard → Tokens.

Troubleshooting

401 Unauthorized on install — Your token is missing, revoked, or your subscription is inactive. Check the _authToken env var referenced in .npmrc is set, and confirm your subscription on Dashboard → Billing.

Installation fails with permission errors — Try running the CLI with elevated permissions or check that your package manager has write access to node_modules.

Yarn Berry (v2+) — Yarn Berry ignores .npmrc. Configure the scope in .yarnrc.yml instead (the CLI prints the exact snippet), and use nodeLinker: node-modules:

.yarnrc.yml
nodeLinker: node-modules
npmScopes:
  blakeui-pro:
    npmRegistryServer: "https://registry.blakeui.pro"
    npmAuthToken: "${BLAKEUI_AUTH_TOKEN}"

Authentication expired — Run npx @blakeui/pro login to re-authenticate. CLI logins last 180 days.

What's Next?

On this page