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

@tree-finder/base

v1.0.4

Published

browser/tree widget implemented as a custom DOM element. Built on top of regular-table

Downloads

77

Readme

A Javascript library for the browser, tree-finder exports a custom element named <tree-finder>, which can be used to easily render filebrowers or other hierarchical trees. Only visible cells are rendered.

Features

  • [x] lazy data model and virtualized rendering -> can support billions of rows
  • [x] tree-like columns
  • [x] multi-sort
  • [x] multi-selection
  • [x] multi-filter
  • [x] built in breadcrumbs
  • [x] full clipboard model, with support for copy/cut/paste between multiple <tree-finder> instances
  • [ ] command hooks to support 3rd party integrations
    • [ ] basic actions
      • [x] open
      • [x] delete
      • [ ] rename
      • [x] copy
      • [x] cut
      • [x] paste
    • [x] integration of command hooks with selection model
  • [ ] icon support
    • [ ] icons-as-svg-elements
    • [ ] icons-as-css-classes
  • [ ] drag-n-drop

Examples - try <tree-finder> out live

|| |:--| |basic| |basic|

Installation

Include via a CDN like JSDelivr:

  <script src="https://cdn.jsdelivr.net/npm/@tree-finder/base/dist/tree-finder.js"></script>
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@tree-finder/base/dist/tree-finder.css">
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@tree-finder/base/dist/theme/material.css">

Or, add to your project via pnpm:

pnpm add @tree-finder/base

... then import into your asset bundle.

import "@tree-finder/base";
import "@tree-finder/base/style/theme/material.css";

Development

  • First, ensure that you have nodejs >= 20.0.0 and pnpm installed
  • Clone this repo
  • Build and run the "simple" example
    cd examples/simple
    pnpm
    pnpm run start

pnpm run start will launch a dev server. Open the url it supplies in any browser in order to view the example. While the dev server is running, any changes you make to the source code (ie any .ts or .less files) will trigger a rebuild, and the example will automatically reload in your browser.

Data Model

A tree-finder instance should be inited with a root directory:

  await treeFinder.init({
    root,
    gridOptions: {
      doWindowResize: true,
      showFilter: true,
    },
  });

Starting from the root, objects should contain at least the field kind which will be dir for directory, or another file type (e.g. text). For directories, it should have a method async getChildren to get the contents of that directory.