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

@jbpark/workbench

v0.3.0

Published

Headless file tree + editor React library, backed by a swappable WorkbenchAdapter data source.

Readme

workbench

npm

English | 한국어

A headless React file tree and editor. Workbench shows a lazily loaded, virtualized file tree next to tabbed editors and gets its files from a swappable WorkbenchAdapter, so the same widget works over a local folder, a REST API or any other source.

Documentation and live demos: https://workbench-guide.vercel.app

Features

  • Any data source. Four adapter methods (getTree, loadChildren, readFile, writeFile) connect a local folder (createFsAdapter), a REST API (createHttpAdapter) or your own store. Directories load one level at a time.
  • Any editor. File tabs, unsaved state and saving work through an engine-neutral renderer contract. Use the CodeMirror editor from @jbpark/workbench/code-editor or bring your own.
  • Headless. No CSS and no class names: every region and state is a data-* attribute.
  • A complete widget. Drag-sortable tabs, a resizable sidebar, read-only mode, and dark and light themes.

Installation

pnpm add @jbpark/workbench

React 19.1.1 or later is a peer dependency. The default editor is a separate entry with optional peers:

pnpm add @jbpark/ui-kit @uiw/react-codemirror @uiw/codemirror-theme-vscode \
  @codemirror/lang-javascript @codemirror/merge codemirror

Usage

import { useState } from 'react';

import {
  Workbench,
  type WorkbenchAdapter,
  createFsAdapter,
} from '@jbpark/workbench';
import { codeEditorRenderer } from '@jbpark/workbench/code-editor';

export function App() {
  const [adapter, setAdapter] = useState<WorkbenchAdapter>();

  const openFolder = async () => {
    // The File System Access API: Chromium-based browsers, HTTPS or localhost.
    const directory = await window.showDirectoryPicker({ mode: 'readwrite' });

    setAdapter(createFsAdapter(directory));
  };

  if (!adapter) {
    return <button onClick={openFolder}>Open folder</button>;
  }

  // The widget fills its parent, which must have a height.
  return (
    <div style={{ height: '100vh' }}>
      <Workbench adapter={adapter} renderEditor={codeEditorRenderer} />
    </div>
  );
}

Workbench renders unstyled markup until you add styles. The Styling page lists every attribute and has a complete Tailwind CSS v4 stylesheet.

| Guide | Covers | | ------------------------------------------------------------------ | ------------------------------------------------------------------------- | | Workbench | Props, saving, tabs, read-only, theme, resizing | | File tree | FileTree on its own, lazy loading, icons | | File editor | FileEditor, the renderer contract, the CodeMirror entry, custom editors | | Adapters | createFsAdapter, createHttpAdapter, writing your own | | Styling | Every data-* attribute, inline styles, a Tailwind CSS v4 stylesheet |

Package entries

| Entry | Contents | | ------------------------------- | --------------------------------------------------------------------------------------------------------------- | | @jbpark/workbench | Workbench, FileTree, FileEditor, createFsAdapter, createHttpAdapter, detectLanguage and their types | | @jbpark/workbench/code-editor | codeEditorRenderer and createCodeEditorRenderer, backed by @jbpark/ui-kit's CodeMirror editor |

Development

Use the Node version in .nvmrc and pnpm.

pnpm install
pnpm dev                    # demo app in demo/ (local folder or mock HTTP source)
pnpm build                  # library bundle and types into dist/
pnpm lint
pnpm check-types
pnpm test
pnpm check-declarations     # built declarations without demo globals

pnpm --dir website install  # the docs site is a separate pnpm project
pnpm --dir website start    # builds the library, then serves the site

How runtime dependencies are split between peerDependencies, dependencies and the consumer is fixed in docs/dependency-policy.md.

Releases use changesets: add one with pnpm changeset in any pull request that changes the published package.

License

MIT