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

@k8slens/public-utilities

v1.1.2

Published

The handful of general-purpose types and helpers that public contracts packages need, published so an outsider can resolve them

Readme

@k8slens/public-utilities

The few general-purpose types and helpers that public contracts packages need in their own signatures.

A contracts package promised to everyone ("visibility": "public-for-all") may only depend on other public-for-all packages, or npm install fails outside this monorepo. @lensapp/utilities is the natural home for a helper like MaybePromise, but it is a large internal kitchen sink and publishing it whole would make every one of its corners a forever public API.

So the minimum moves here, and @lensapp/utilities re-exports it. There is one definition of each symbol, in this package; internal code keeps importing it from @lensapp/utilities exactly as before.

What belongs here

Only a symbol that appears in the public surface of a public contracts package — a token's type, a factory's parameters, an exported interface. That is the whole admission rule.

Nothing else: this package is a forever public API, so every symbol added is a promise that cannot be quietly withdrawn. When a public contract needs a general-purpose helper, move that one helper here and re-export it from @lensapp/utilities; do not move its neighbours along for symmetry.

What is here

| Symbol | Why it is public | |---|---| | MaybePromise<T> | Contracts model factories that may resolve later | | AsyncVoidFunction, MaybeAsyncVoidFunction | Menu and action contracts take handlers that may be async | | expectDefined | Contracts that read a React context assert it is present |