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

@shadow-library/sdk

v0.1.0

Published

Shared Shadow Library novel vocabulary (genres, tags, content ratings) and the cross-app publishing content-hash contract

Readme

@shadow-library/sdk

Shared vocabulary and wire contracts for the Shadow Library novel platform. The package has no runtime dependencies, and the root entrypoint has no Node built-ins either, so it is safe in a browser bundle.

import { NOVEL_GENRES, NOVEL_TAG_GROUPS, isRatingAtMost, type ContentRating } from '@shadow-library/sdk';
import { chapterContentHash } from '@shadow-library/sdk/publishing';

| Subpath | Contents | | -------------------------------- | -------------------------------------------------------------------------------------------- | | @shadow-library/sdk | Genres, tags and their groups, and the three graded content-rating dimensions. Browser-safe. | | @shadow-library/sdk/publishing | The canonical content-hash primitive and the chapter hash derivation. Uses node:crypto. |

Content ratings are three independent ordered dimensions (sexualContent, violence, darkContent). Each is optional on a novel and an absent dimension means unrated, which is never the same as 'none' — the comparison helpers accept only a concrete level, so an unrated dimension has to be narrowed first.

Publishing

The published artifact is the build output, never this directory — the root .gitignore excludes dist/, and npm falls back to it without an .npmignore, so packing the source directory yields a tarball with every exports path pointing at a file that was ignored. A prepublishOnly guard fails that route; publish the built package instead (scripts/build.ts synthesizes dist/package.json without the guard):

bun scripts/build.ts packages/sdk && npm publish packages/sdk/dist