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

@spup/mod-builder

v2.0.0

Published

Builds and checks a mod for Shy's Power-Up Factory

Readme

@spup/mod-builder

Builds and checks a mod for Shy's Power-Up Factory.

Commands

Run them in your mod: the mod is the working directory, it builds into ./dist, and the version is the one in your package.json. Every default can be overridden — build <mod dir> <out dir>, check <package dir>, --version <x.y.z>.

  • build — writes dist/mod.js and dist/mod.json. Optional --homepage <url> goes into the manifest. The bundle is minified (class names kept — the wire codec names each message and event type after its class); --minify false keeps it readable, which is what the dev server builds with. The minifier is pinned to an exact version here, so the same source hashes the same from any machine.
  • check — what a registry listing must pass: the manifest parses, the bundle reaches no global outside a small pure-computation whitelist (fetch, document, eval and friends fail here), the declared parts match the exported factories, and the declaration and sim factories evaluate against a stub SDK.
  • scan — just the free-variable scan, for a quick look at a bundle.

check proves a package loads and behaves at its edges; it cannot prove the content is valid, since that needs a running engine. The registry runs it on every published version, and a maintainer reads the source besides.