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

@salo/core-ui

v3.1.0

Published

Core Salo React UI library

Readme

core-ui

Publish Development

The core ui is developed in order to give components with limited styling that can be used on all Salo projects. Where appropriate props can be exposed to modify the appearance. In order to aid styling from within projects it is also important that components are given structured class names that can be used for override styles in different applications.

Development

The project uses storybook for local, abstracted development which has been configured to work with the GraphQL gateway. All components must have README.s and appropriate stories with knobs.

To get started run the following to install the dependencies

yarn

Then run the demo command to run the initial unit tests and boot up the development server

yarn demo

Hooks

useAnalytics

Example usage:

useAnalytics({
  event_type: 'user_profile_view',
  content_id: id,
  content_type: 'user',
  url: isBrowser && window.location.href
});

It returns the call to the mutation so you can also do the following:

const runAnalytics = useAnalytics({
  defer: true
});

// later
runAnalytics({
  variables: {}
})

Publishing

  1. Create a feature branch from master
  2. Open a PR from your feature back to master
  3. When you are ready to release the library checkout master and pull down the latest code.
  4. run yarn release locally to add changelog and increment version number and then push directly to master to trigger publish action
  5. If you want to deploy to GitHub pages then run yarn release:ghp. This should only be run from master so not before a PR is merged