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

@djangocfg/widget-data

v0.1.9

Published

Data surfaces: file tree, JSON viewer, data grid and table, kanban, listbox, masonry and timeline

Downloads

2,101

Readme

@djangocfg/widget-data

The surfaces that put rows, nodes and cards on screen: a file tree, a JSON viewer, a data grid and table, a kanban, a listbox, a masonry and a timeline.

Install

pnpm add @djangocfg/widget-data @djangocfg/ui-core
import { FinderTree } from '@djangocfg/widget-data/tree';
import '@djangocfg/widget-data/styles';

The styles import is not optional: Tailwind v4 does not scan node_modules, so without it every surface here renders unstyled.

Subpaths

| Subpath | What | Own docs | |---|---|---| | ./tree | TreeRoot, FinderTree — generic, slot-driven, async, with Finder CRUD | src/Tree/README.md | | ./file-icon | FileIcon, getFileIcon, createFileIconSlot | — | | ./json-tree | JsonTree — collapsible JSON with search and copy | src/JsonTree/README.md | | ./data-grid | DataGrid — sorting, filtering, pagination, selection | src/DataGrid/README.md | | ./data-table | DataTable — the same, as a semantic <table> | src/DataTable/README.md | | ./kanban | Kanban — columns and cards, drag included | — | | ./listbox | Listbox — a composable selection primitive | — | | ./masonry | Masonry — a column layout | src/Masonry/README.md | | ./timeline | Timeline — an ordered event column | — |

Each subpath also exports its Lazy* wrapper (LazyTree, LazyDataGrid, …) for a surface that should not be in the entry chunk.

Prefer a subpath to the root. The root barrel exists and works, but pulls all nine trees; an app that wants a tree should ask for the tree.

Grouping

One package rather than nine, because these share a shape rather than a library: none of them carries a heavy dependency the others would pay for. The whole external surface is @dnd-kit/core (Tree only), three small Radix and cva utilities, and lucide-react.

FileIcon lives here rather than with the visual widgets because it is a Tree slot — createFileIconSlot types against TreeRowSlot, and separating them would put a package boundary through one component's two halves.

Verify

pnpm --filter @djangocfg/widget-data check-types test