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

johnnymiller

v0.0.5

Published

Johnny Miller's personal website.

Readme

Johnny Miller's Website

Johnny Miller's personal website.

Johnny Miller

Development

The following is a bunch of rambled thoughts that I wanted to make sure to record and not forget, but I'll come back to later and better organize.

Environment Variables

The Johnny Miller website uses rollup-plugin-replace for environment variable replacement. Any environment variable prefixed with JM_ will automatically be replaced in the code if it's listed as a process.env.* variable. For example:

process.env.JM_JWT_SECRET

Is replaced with with the JWT secret.

process.env.NODE_ENV and process.env.PORT are the only non-prefixed variables to also be replaced.

Deploying

We're currently deployed on Google Cloud Run.

Environment Variables

We're using a Google Cloud keyring to encrypt variables and import them directly in an encoded .env.enc file. If you need to add, change, or delete any environment variables, make sure the .env.enc-source file exists with all appropriate environment variables, then run:

yarn run keyring

That will encrypt the environment variables. Then commit the changes to .env.enc to this repo, and deploy as normal.

Deploying Changes