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

@panphora/hyperclay-workspace

v0.2.1

Published

Shared Hyperclay workspace shell, built. Used by hyperclay.com and Hyperclay Local.

Readme

@panphora/hyperclay-workspace

The shared Hyperclay workspace shell. hyperclay.com's dashboard and the Hyperclay Local app both depend on this package, so the two hosts render the same document list, frame bridge and workspace chrome.

Contents

This package ships built output only. Every file under dist/ is generated by esbuild and tsc, minified, with no source, no sourcemaps and no declarations that point at the repository that produced them. The package is not open source. It is published under the UNLICENSED license and the source itself lives in a private repository.

Install

npm install @panphora/hyperclay-workspace

react and react-dom are peer dependencies:

{
  "peerDependencies": {
    "react": "^19.2.3",
    "react-dom": "^19.2.3"
  }
}

Import built modules by path, with no extension:

import { workspaceKeys } from '@panphora/hyperclay-workspace/query-keys';
import '@panphora/hyperclay-workspace/workspace.css';

Development

The source of truth is the private hyperclay repository. This package is a projection of its dashboard/workspace, dashboard/ui and shared/workspace directories, plus the vendored Bevel snapshot used to build and test it.

npm install
npm run sync   # copy the source out of a sibling ../hyperclay checkout
npm run build  # build dist/ through esbuild and tsc
npm test       # build:check, then the jest suite

npm run sync takes --hyperclay <path> to point at a checkout somewhere other than ../hyperclay. It rewrites every relative import to the package layout and refuses to finish if an import points at a file the package does not carry.