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

jogalanza-ui-kit

v0.0.0

Published

Shared Vue 3 component library, distributed as independent npm packages published to GitHub Packages under the `@jogalanza` scope. npm workspaces monorepo:

Readme

jogalanza/ui-kit

Shared Vue 3 component library, distributed as independent npm packages published to GitHub Packages under the @jogalanza scope. npm workspaces monorepo:

packages/
  core-ui/      @jogalanza/ui-kit-core — shared shadcn-vue primitives (Badge, Button, Checkbox,
                Dialog, DropdownMenu, Input, NativeSelect, Popover, Separator, Switch, Table,
                Toaster), the cn() util, and the notify()/notifyError()/notifyResult() toast
                helpers. Dual-purpose: published directly (for projects that want the primitives
                on their own) AND bundled into other ui-kit packages at build time (e.g.
                filterbar), so those stay fully self-contained without their own peer dependency.
  filterbar/    @jogalanza/filterbar — badge-style popover filter bar.

Adding a new component package

  1. packages/<name>/ with its own package.json (copy packages/filterbar/package.json as a template — same peerDependencies, same publishConfig pointing at GitHub Packages) and vite.config.js (copy packages/filterbar/vite.config.js; keep peer deps external, leave @jogalanza/ui-kit-core bundled).
  2. Add "@jogalanza/ui-kit-core": "*" to its devDependencies (not dependencies — it's bundled at build time, so it should never be installed separately by consumers of the leaf package) and import primitives from it, e.g. import { Button, Popover } from '@jogalanza/ui-kit-core'. A project that wants core-ui's primitives directly (not through a leaf package) can instead add @jogalanza/ui-kit-core as a normal dependency.
  3. If the component needs a primitive that doesn't exist in core-ui yet, add it there (not locally) so future components can reuse it too.
  4. npm install at the repo root to link the new workspace. Build core-ui before any package that bundles it (npm run build --workspace=packages/core-ui first) — its main/exports point at its own built dist, not raw source.

Develop

npm install
npm run build --workspace=packages/<name>