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

@bengsfort/stdlib

v0.2.0

Published

A collection of utilities that I am tired of re-implementing

Readme

@bengsfort/stdlib

A collection of utilities that I got tired of re-implementing.

Architecture

This package is written for use in ES Module environments. It should work out-of-the-box with projects using a bundler like Vite, Rollup, or ESBuild. Currently CommonJS is not supported, but will be in the future if a need arises.

Platform-specific modules

All top-level utilities should be considered safe for all modern js-based runtimes. They should not include any runtime-specific logic or API's, and any runtime-specific modules can be found in respective /node or /browser directories.

For example, the logging utility module is runtime agnostic, whereas the node/logging utility module is altered to provide more features when running in node, and imports from node:console to do so.

// Something running in the browser or non-node environment
import { makeLogger } from '@bengsfort/stdlib/logging';

// Something running in node that wants node-specific features
import { makeLogger } from '@bengsfort/stdlib/node/logging';

Releasing

Automated Release Flow

Once a PR hits main, the release workflow will trigger and any changesets will be handled automatically.

Manual Release Flow

  1. When a new feature or change has been made, run pnpm changes:add to create a changeset (this should be commited).
  2. When ready to release, run pnpm changes:commit to apply all changes and update changelogs.
  3. Run pnpm install to update lockfile and rebuild packages.
  4. Commit and run pnpm ci:publish to publish.