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

cedar-ui-kit

v1.1.29

Published

### 1. In the `ui-kit` project - Link the package: ```sh pnpm link --global ``` ```sh pnpm run build ``` ⚠️ The consuming project uses the dist/ output. If you don’t build, changes won’t appear.

Readme

📖 UI Kit

1. In the ui-kit project

  • Link the package:
pnpm link --global
pnpm run build

⚠️ The consuming project uses the dist/ output. If you don’t build, changes won’t appear.

2. In the consuming project (the app where you use the UI Kit)

  • Link the local UI Kit:
pnpm link cedar-ui-kit

(adjust the path if your UI Kit folder is located elsewhere)

  • After each update in ui-kit, repeat:
# inside ui-kit
pnpm run build

# inside your app
pnpm install

📦 Publishing to npm registry

Prerequisites

  • Node.js and pnpm installed
  • npm account (create one at https://www.npmjs.com/signup)
  • Logged in to npm in your terminal

Publishing Steps

  1. Login to npm (if not already):

    npm login

    Enter your username, password, and email when prompted.

  2. Build the package:

    pnpm run build

    This ensures the latest version of your components is compiled into the dist/ directory.

  3. Update the package version:

    pnpm version patch
    • Use patch for bug fixes, minor for new features, and major for breaking changes.
    • This command automatically updates your package.json version and creates a Git tag.
  4. Publish to npm:

    pnpm publish --access public
  5. Verify the publish: Visit https://www.npmjs.com/package/cedar-ui-kit to confirm that your latest version is live.

  6. (Optional) Push tags and commits to Git:

    git push && git push --tags

🧩 After Publishing

  • In the consuming project:
    pnpm install cedar-ui-kit@latest
    or to upgrade to the latest version:
    pnpm update cedar-ui-kit