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

tembro

v3.1.6

Published

Reusable React UI kit with dashboard-ready components, CLI registry helpers, and TypeScript support.

Readme

tembro

tembro is a source-copy-first React UI kit.

The CLI copies editable component source into your app. New projects should treat local components code as the canonical surface.

Start

Next.js:

npx tembro init --template next --defaults
npx tembro add button input

Vite:

npx tembro init --template vite --defaults
npx tembro add button input

Use

After add, import from local app source:

import { Button } from "@/components/ui/button"
import { Input } from "@/components/ui/input"

Core rule

  • init sets up config and theme tokens.
  • add copies component source into your app.
  • Local source is the product surface.
  • Runtime package import is compatibility-only, not the main path.

Component model

Every public surface is a component. Repeated behavior should be handled with props, hooks, helpers, and local source files, not separate family abstractions.

Migrating to 3.0

Replace compatibility component imports with the canonical API:

// before
<FormNumberInput control={control} name="price" />
<FormAsyncSelect control={control} name="ownerId" loadOptions={loadOwners} />
<AppSidebar items={items} />
<SmartCard title="Account" />

// after
<FormInput control={control} name="price" kind="number" />
<FormSelect control={control} name="ownerId" kind="async" loadOptions={loadOwners} />
<Sidebar items={items} />
<InfoCard title="Account" />

The CLI still accepts old component names and redirects them to canonical source-copy entries. Removed incomplete components do not have drop-in replacements; use a production-grade implementation only when the application actually needs that interaction.

Production interaction components

Install the new drag-and-drop and virtualization surfaces through the CLI:

npx tembro add sortable-list kanban virtual-list data-table
  • SortableList supports pointer, touch, and keyboard reordering with controlled or uncontrolled state.
  • KanbanBoard moves cards within and across columns, including empty columns and canceled operations.
  • VirtualList keeps large collections responsive by mounting only the visible window.
  • DataTable enables row virtualization with virtualization={{ height: 480 }}.

Current direction

The docs layer is being rebuilt from scratch around:

  • source-copy workflow
  • fewer public component names
  • stronger component quality
  • simpler theming and API contracts

Local verification

npm run lint
npm run build
npm run test:run