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

@kelpie/ui

v0.23.0

Published

React UI for Kelpie: components, pages, API client, and the extension registry an assembly composes modules through.

Readme

@kelpie/ui

The React UI for Kelpie.

Kelpie is an open-source, agent-native CRM and company brain. This package holds the components, the pages, the typed API client, and the extension registry that an assembly composes modules through. It talks to the same public API agents use; there are no private UI-only endpoints.

Install

npm install @kelpie/ui react react-dom

React 19 is a peer dependency, so it resolves to your copy rather than a second one.

Use

import { KelpieApp, registerUiModules } from '@kelpie/ui'
import '@kelpie/ui/styles.css'
import { StrictMode } from 'react'
import { createRoot } from 'react-dom/client'

import { uiModules } from './kelpie.ui.config.ts'

createRoot(document.getElementById('root')).render(
  <StrictMode>
    <KelpieApp extensions={registerUiModules(uiModules)} />
  </StrictMode>,
)

Registration happens once, above the root, at build time. A module clashing with another fails at startup rather than as a tab someone notices is missing a week later.

Styling

@kelpie/ui/styles.css imports Tailwind CSS 4 and declares the theme tokens every component uses. Your build needs to process it with Tailwind, for example through @tailwindcss/vite.

The stylesheet carries an @source directive pointing at the components beside it, which is how Tailwind finds the classes they name. Tailwind skips node_modules when it detects sources by itself, so that directive is doing real work. If it ever stops, the build still succeeds and every page renders unstyled.

Colours are tokens rather than literals, so light and dark are the same markup against a different :root block, and a module replacing a component inherits the palette.

Licence

AGPL-3.0-only.