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

@hashintel/ds-components

v0.2.2

Published

HASH Component Library built with React, Ark UI, and PandaCSS

Readme

@hashintel/ds-components

React components for HASH's design system, built with TypeScript, Ark UI, and PandaCSS.

Ownership Model

As of the FE-612 ownership restructure:

  • @hashintel/ds-components owns the Panda preset source, token/codegen scripts, and demo surfaces.
  • @hashintel/ds-helpers is the generated Panda styled-system artifact.
  • The old @hashintel/ds-theme surface has been folded into @hashintel/ds-components/preset.

For new internal work, treat ds-components as the source of truth.

Public Entry Points

| Entry point | Purpose | | --------------------------------- | ------------------------------------------------------------------------------ | | @hashintel/ds-components | Published component entrypoints from src/components/*.tsx | | @hashintel/ds-components/preset | Panda preset helpers such as preset, createPreset, and scopedThemeConfig | | @hashintel/ds-components/tokens | Package-owned Panda token objects such as tokens and semanticTokens |

Component implementation still uses the generated Panda runtime from @hashintel/ds-helpers:

import { css, cva, cx } from "@hashintel/ds-helpers/css";
import { Box, Flex, Stack } from "@hashintel/ds-helpers/jsx";

Token lookup helpers and token types should still come from @hashintel/ds-helpers/tokens. Use @hashintel/ds-components/tokens when you need the package-owned Panda token objects themselves.

Package Layout

| Area | Location | | -------------------------- | -------------------------------- | | Components | src/components/** | | Panda preset source | src/preset.ts, src/preset/** | | Package token facade | src/tokens.ts | | Token and color generators | scripts/** | | Stories | src/components/*/*.stories.tsx | | Token demo stories | src/tokens/** | | Intro docs | src/stories/Intro.mdx | | Local demo config | panda.local.config.ts | | Ladle harness | .ladle/** | | Snapshot tests | tests/** |

Common Commands

Run these from libs/@hashintel/ds-components:

yarn dev
yarn dev:lib
yarn codegen
yarn lint:eslint
yarn lint:tsc
yarn test:unit
yarn test:snapshots
yarn build

yarn dev is the primary Ladle-based review loop. Use yarn dev:ladle for component-story review and yarn dev:lib when you only need the library watcher. yarn prepare/yarn codegen generates the shared ../ds-helpers/styled-system authoring runtime, and the demo loops rely on Vite/PostCSS for CSS extraction while the server is running.

Contributor Docs

External References