npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

banhaten

v0.1.3

Published

Banhaten design system: an Arabic and English-first React design system with shadcn-style component installation.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ahmedgalalahmedgalal

Keywords

banhatendesign-systemreactshadcnrtlarabiccomponents

Readme

Banhaten Design System

Banhaten is an Arabic and English-first React design system with source-installed components, generated design tokens, and first-class RTL behavior. It uses a shadcn-style distribution model without copying shadcn visuals: components are built around Banhaten tokens, Banhaten component aliases, and Banhaten Figma-derived interaction patterns.

Quick Start

Run the CLI from the root of a React app:

npx banhaten init
npx banhaten add button input select

When dependencies are added, the CLI prints the install command for your package manager.

npm install
pnpm install
yarn install
bun install

What Init Adds

banhaten init writes:

  • banhaten.config.json with schema-backed aliases.
  • The base cn utility and use-direction hook.
  • The generated Banhaten token stylesheet in your configured CSS file.
  • Tailwind v4 and Vite alias setup when those files are detected.
  • Required package dependencies.

banhaten add and banhaten update also refresh the generated token stylesheet, so installed projects receive token changes as the registry evolves.

CLI

npx banhaten init [--cwd <path>] [--force] [--dry-run]
npx banhaten add <component...> [--cwd <path>] [--force] [--dry-run]
npx banhaten diff [component...] [--cwd <path>] [--force]
npx banhaten update [component...] [--cwd <path>] [--force] [--dry-run]
npx banhaten list [--json]
npx banhaten search <query> [--json]
npx banhaten docs <component> [--json]
npx banhaten view <component> [--file <registry-source>] [--json]
npx banhaten version

Global flags:

  • --cwd <path> runs against another project directory.
  • --dry-run previews writes.
  • --force rewrites generated files even when already current.
  • --json prints machine-readable output where supported.
  • --silent or -s suppresses normal command output.
  • --yes or -y is accepted for non-interactive scripts.
  • --version or -v prints the CLI version.

Generated File Ownership

Banhaten is a source registry. Installed component files are generated from the registry and are replaceable by banhaten add or banhaten update when registry content differs.

Use banhaten diff before updating if you edit generated component files locally:

npx banhaten diff
npx banhaten update button

Keep product-specific composition outside generated files when possible. Use local wrapper components for app behavior and keep Banhaten files focused on tokens, layout, accessibility primitives, and direction behavior.

Tokens

Every component must style through Banhaten CSS variables, component aliases, or documented exception-ledger values. Raw colors, pixel values, opacity utilities, z-index utilities, durations, and shadow literals are blocked by the component token check.

Token modes:

  • Color mode: light and dark.
  • Brand theme: blue, gray, brown, orange, green, purple, teal.
  • Radius mode: default, rounded, sharp.
  • Direction: inherited LTR or RTL, with component-level dir support where needed.

Example:

<html className="dark" data-theme="brown" data-radius="rounded" dir="rtl" lang="ar">

Typography utilities are generated as .bh-text-* classes and map directly to token variables.

<h1 className="bh-text-heading-xl-bold">...</h1>
<p className="bh-text-body-md-regular">...</p>

Registry Formats

Banhaten maintains two registry artifacts:

  • registry/index.json is the Banhaten source of truth used by the Banhaten CLI. It includes rich metadata for RTL behavior, parts, examples, files, and dependencies.
  • registry.json is a generated shadcn-compatible export for tools that expect the public shadcn registry schema.

Regenerate the shadcn-compatible export after registry changes:

npm run registry:export

Documentation

Primary docs live in the playground and render live registry-backed previews, install commands, source snippets, API tables, registry files, RTL behavior, and copyable code panels.

Markdown docs live in docs/design-system/components. They are checked for install, API, examples, token contract, RTL rules, and accessibility sections.

Useful commands:

npm run docs:check
npm run docs:normalize
npm run playground:dev

Components

The registry includes core primitives such as Button, Input, Select, Field, Modal, Sheet, Sidebar, Menu, Tabs, Toast, Table, and Chart. It also includes Banhaten-specific and product-oriented components such as Attribute, Radio Card, Progress Slider, Social Button, Tag, Toolbar, Timeline, Banner, File Upload, Page Header, Command Bar, Slideout, Activity Feed, and Steps.

Expanded components are larger app compositions. They are installed through the same CLI but documented as a separate tier because their layout contracts are broader than primitive controls.

Development

npm run check
npm run tokens:check
npm run registry:check
npm run playground:test

The full check verifies CLI behavior, generated token CSS, token contract, raw token violations, registry mirrors, shadcn-compatible registry export, markdown docs, and playground coverage.