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

@snootclub/post-receive

v0.3.0

Published

a post receive hook for deploying

Readme

snoot.club/post-receive

a post receive deploy hook for snoots

usage

put npx @snootclub/post-receive in your serve-side repo's hooks/post-receive

snoot usage

for default snoot behaviour you can do something like this inside your snoot container:

git init --bare /repo
>/repo/hooks/post-receive cat <<.
#!/bin/sh
npx @snootclub/post-receive
.
chmod +x /repo/hooks/post-receive
cd /application
git remote add origin /repo
git add .
git push

now you'll be able to do this on your local machine:

git clone ssh://snoot.club:$MY_PORT/repo snoot

and when you push up any changes in snoot it will install them, build them and make them live.

advanced usage

this isn't really specific to snoots and there are some options avaiable

--deploymentDirectory

the directory to use as the deployment target, where files are served from by the webserver.

default /application

--deploymentBranch

the only brank acceptable to deploy from. if changes are pushed to any branch other than this, they won't be deployed ^_^

default master

--repoDirectory

the source bare repo directory used when deploying. by default this uses the directory the process is running from, which will be the current repo when used in a git hook :)

default process.cwd()