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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@hashintel/ds-components

v0.0.1-c

Published

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

Readme

@hashintel/ds-components

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

LLM-Driven Development

Component development is primarily handled by LLM coding assistants (GitHub Copilot, Claude, etc.) using the CONTRIBUTING.md as instructions.

For LLM Assistants

See CONTRIBUTING.md for complete implementation instructions including:

  • Figma design context retrieval via MCP
  • Ark UI pattern integration
  • Design token mapping
  • Component structure and patterns
  • Storybook stories creation

For Human Developers

Use LLM assistants to add or update components. Direct manual implementation is only needed for:

  • Complex edge cases beyond current LLM capabilities
  • Bug fixes requiring deep debugging
  • Architectural changes

Quick setup:

  1. Ensure Figma Desktop app is running with the design file open
  2. Have Figma MCP Server configured in Figma app
  3. Have Ark UI MCP Server configured in your User MCP config (not committed to repo)
  4. Select the component in Figma you want to implement
  5. Ask your LLM assistant to implement the component
  6. Review the component in Storybook to verify rendering and behavior match the design
  7. Make manual adjustments if needed for edge cases or visual refinements

Design System Architecture

Design Tokens: Defined in @hashintel/ds-theme package, synchronized from Figma variables

Token Mapping: figma-to-panda-mapping.json (automatically generated) translates Figma variables to PandaCSS tokens

Styling System: PandaCSS provides type-safe styling with design tokens fully type-checked at compile time. Invalid tokens or outdated token names (from Figma updates or mapper changes) will produce TypeScript errors, ensuring design system consistency.

Component Base: Built on Ark UI for accessibility and behavior patterns

External Resources