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

@xqmsg/ui-core

v0.30.0

Published

Build the library: ``` pnpm build ```

Downloads

706

Readme

Local development

Build the library:

pnpm build

Storybook (port 6006):

pnpm storybook

Watch mode:

pnpm start

Testing a local build in another project

In the consuming project's package.json, point at the local path:

"@xqmsg/ui-core": "file:../ui-core"

After any change, rebuild and reinstall:

pnpm run build
rm -rf node_modules/@xqmsg && pnpm i

Creating a PR

Branch off master with a descriptive name. Commit with a signed message so changes are attributable.

Releasing a new version

  1. Update the changelog — add a summary entry to CHANGELOG.md and a dated detail file to Changelog/. See existing entries for the format.
  2. Bump the version in package.json manually, or:
    npm version [patch|minor|major] --no-git-tag-version
  3. Commit and tag:
    git add CHANGELOG.md Changelog/ package.json
    git commit -m "chore: release vX.Y.Z"
    git tag vX.Y.Z
    git push origin && git push origin --tags

Do not use the release:patch / release:minor / release:major scripts — they auto-generate and overwrite CHANGELOG.md, breaking the manual Changelog/ workflow.

Publishing to npm

From master, after a clean install:

pnpm run clean && pnpm install && pnpm run build && npm publish