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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@olehermanse/utils

v0.1.12

Published

Utility functions in js / ts

Readme

Common js / ts utilities for personal use

I use these across a few different projects;

  • https://github.com/olehermanse/trpg
  • https://github.com/olehermanse/tpg
  • https://github.com/olehermanse/towers

Publishing new versions

Here are the steps to make a new version:

  1. Check that package.json has the correct version: https://github.com/olehermanse/utils/blob/main/package.json#L3
    • It should be the version you want to release.
    • Change it if necessary, for example to bump major or minor version.
  2. Create a release in GitHub:
    • Open https://github.com/olehermanse/utils/releases
    • Draft a new release
    • Put the version number in both tag (create a new tag) and name field
    • Generate release notes
  3. Check that the release has been published on npm:
    • https://www.npmjs.com/package/@olehermanse/utils
    • This is done automatically by the GitHub Action after creating a release.
  4. Check that the version number has been bumped:
    • https://github.com/olehermanse/utils/commits/main/
    • The GitHub Action will automatically push a commit bumping the patch version.
    • Manually bump minor or major version if you know that is what you'll release next:
      • https://github.com/olehermanse/utils/blob/main/package.json#L3

Token for publishing to npmjs.com

One secret is needed for the publishing action to work - NPM_TOKEN. After logging into npmjs.com it is generated here:

https://www.npmjs.com/settings/olehermanse/tokens

I use a granular token with access to only this repository, and expiration of ~1 year. This is entered into GH UI here:

https://github.com/olehermanse/utils/settings/secrets/actions

The token is not stored anywhere else and must be regenerated if expired or compromised.