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

@autofleet/shtinker

v3.13.22

Published

Readme

Shtinker

Breaking Changes in V2

  • No code changes are required for services using this package.
  • Fixed a bug where the context entity ID was incorrectly set to the ID of the last entity saved to the database under the same context. Now, the entity ID will only change when the entity type of the context matches the model name during the save operation to the database.

V3 migration

The breaking change in this version is the removal of zehut from dependencies and usage as a peer-dependency. The required version of zehut is now ^4.0.0.

This was moved to being a peer-dependency in order to ensure that the version of zehut used here is the same as used in the MS, and not risk the package using v4 while the service is using v3, which would cause zehut to have multiple traces, which will not all hold the correct data.

Additionally, the minimum node version is now 18, due to the minimum version of node defined in zehut.