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

@qumra/fanar

v0.0.14

Published

Qumra's Arabic-first component library and design tokens. Tailwind 4, RSC-safe.

Readme

@qumra/fanar

Qumra's component library and design tokens — Arabic-first, Tailwind 4, RSC-safe.

Every component works in both dir="rtl" and dir="ltr" with no direction-specific code: logical properties only, and the library reads its own language from <html lang>.

pnpm add @qumra/fanar

Entry points

The package is one install with seven entry points. Importing @qumra/fanar pulls in neither TipTap, nor three, nor the notification system — each heavy group is behind its own path.

| Import | What it gives you | Notes | | --- | --- | --- | | @qumra/fanar | Components | client | | @qumra/fanar/lib | Pure helpers (cn, toLatinDigits) | server-safe | | @qumra/fanar/tokens | Token values (TOKENS, scales) | server-safe | | @qumra/fanar/notifications | Notification system | client | | @qumra/fanar/ai | Assistant surfaces | needs @qumra/jawab-ai | | @qumra/fanar/orb | Animated voice orb | needs three, @react-three/fiber, @react-three/drei | | @qumra/fanar/editor | Rich-text editor | bundles TipTap |

Plus two stylesheets: @qumra/fanar/tokens.css and @qumra/fanar/editor.css.

Setup

/* styles.css */
@import 'tailwindcss';
@import '@qumra/fanar/tokens.css';
import { Button, Money } from '@qumra/fanar'
import { cn } from '@qumra/fanar/lib' // usable from a server component
import { TOKENS } from '@qumra/fanar/tokens'

;<Button variant="primary">
  Pay <Money value={1250} currency="EGP" />
</Button>

The six rules

Every component in this library follows them, and two are enforced by lint:

  1. No hand-written colors. Every color comes from a token.
  2. Surfaces use semantic tokensbg-surface, text-ink, border-line. These flip themselves in dark mode.
  3. Logical properties onlyps-4 not pl-4, start-0 not left-0.
  4. Real elements. Anything clickable is a <button> or an <a>; every field is a <label htmlFor> plus aria-describedby for its error.
  5. Numbers carry data-numeric — pins LTR direction and turns on tabular-nums.
  6. Sizes come from the scaletext-ui, rounded-card, shadow-modal.

Peer dependencies

react and react-dom are required. tailwindcss, three, @react-three/fiber, @react-three/drei, @google/model-viewer, and @qumra/jawab-ai are optional — you only install the ones whose entry point you actually import.

This is not a formality. @react-three/drei pulls in camera-controls, which requires Node 22; as a hard dependency it broke yarn install on a Node 20 server for a consumer that never imported the orb. Heavy groups belong to their entry point, and the manifest has to say so.

Documentation

Source, decision log, and a live catalogue with a page per component live in the repository. Comments and internal docs there are written in Egyptian Arabic: they are the record of why each decision was made, kept in the language the team argued them in.

License

UNLICENSED — see package.json.