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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@snootclub/create-snoot

v1.0.4

Published

snoot club

Readme

Create snoot

the snoot maintenance module

This is the module used on the snoot.club server for creating and working with snoots.

It's specific to the setup of that server and would need changes in order to be useful to anyone else, but the code is here should anyone ever want to look at it or reuse any of the code.

It would be nice to make the non-specific parts of it work without running in that environment, so one could have a local snoot setup, but

commands

snoot create

create a new snoot.

this starts an interactive prompt that asks you some questions.

first it will celebrate that there is a new snoot:

oh, a new snoot? 💕

then it will ask for a name, and a githubUsername.

? what's their name?
? what's their github username?

it'll grab their authorized_keys file from https://github.com/${githubUsername}.keys

then it will let you edit their authorized_keys in your $EDITOR so you can add any others you've been provided.

once it's gathered all that snoot data, it will create them a unix user with that name, putting them in the groups common and undercommon.

the tool will then create them a base application at /www/snoot.club/snoots/${name}. at the moment this base application is defined in the skeletons file. in brief, it has:

  • snoot.json — some meta data about a snoot
  • nginx.conf — an nginx configuration that defers mostly to blocks defined at snootclub/nginx.conf
  • application/package.json — an npm package manifest that uses boop for build, watch and install and zeit's micro for start
  • application/index.js — entry point that defers to boop
  • application/website/index.html — a template html page that tells you how to access your new snoot

then it binds👀 the website directory into the snoot's sftp chroot root

and it boots👢👢 the snoot container

and then it restarts nginx, and updates the next snoot port file.

a few seconds later, the snoot has boot and is ready to toot

snoot ls

list the names of all the snoot, separated by newlines.