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

@bandf/framework-ui

v1.6.0

Published

React UI component library for the bandf framework.

Readme

@bandf/framework-ui

@bandf/framework-ui is the React component layer for BandF apps. It ships raw JSX primitives, BandF-specific components, and the cn() class helper for Parcel to compile inside each app.

Contents

Use components

Generated React apps use per-component imports:

import { Button } from "@/components/ui/button";
import { Card, CardContent, CardHeader, CardTitle } from "@/components/ui/card";

export function ProfileCard() {
  return (
    <Card>
      <CardHeader>
        <CardTitle>Profile</CardTitle>
      </CardHeader>
      <CardContent>
        <Button>Save</Button>
      </CardContent>
    </Card>
  );
}

The root barrel is also available:

import { Button, Card, cn } from "@bandf/framework-ui";

Most primitives follow shadcn conventions: named exports, Radix behavior where appropriate, class-variance-authority variants, Tailwind classes, refs, and a caller-provided className.

Configure aliases and Tailwind

The React templates include the required aliases in tsconfig.json:

{
  "compilerOptions": {
    "paths": {
      "@/components/ui/*": [
        "../../node_modules/@bandf/framework-ui/components/ui/*"
      ],
      "@/lib/utils": ["../../node_modules/@bandf/framework-ui/lib/utils"]
    }
  }
}

Tailwind must scan package JSX as well as app JSX:

export default {
  content: [
    "./views/**/*.{js,jsx}",
    "../../node_modules/@bandf/framework-ui/**/*.{js,jsx}",
  ],
};

The package deliberately ships source JSX. Parcel performs the application build, which keeps one transformation pipeline and lets Tailwind discover the exact classes used by imported components.

Theming

Components consume semantic CSS variables such as --background, --foreground, --primary, --card, and --border through Tailwind mappings. Generated apps define those variables as space-separated HSL channels:

:root {
  --background: 0 0% 100%;
  --foreground: 222 47% 11%;
  --primary: 221 83% 53%;
}

Store channels only, not a complete hsl(...) value, hex color, or named color; the Tailwind theme wraps each token with hsl(var(--token)). Keep a corresponding .dark value in sync when the app supports dark mode.

Package boundaries

React 19 and React DOM 19 are peer dependencies supplied by the app. Component dependencies are package dependencies and require no app-level wiring beyond the template's aliases, Tailwind scan path, and theme.

The root barrel intentionally omits modules whose exports collide:

  • components/ui/bf-floating-panel.jsx re-exports common form and header names;
  • components/ui/sonner.jsx and components/ui/toaster.jsx both export Toaster.

Import those modules through their explicit subpaths. All package files are available below the wildcard export.

Related links