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

@fouaden/snipit

v1.1.2

Published

A lightweight CLI tool to save, search and tag code snippets locally. Stop re-typing; start snipping.

Downloads

323

Readme

snipit 📎


Why snipit?

You know that one-liner you Google every time? The tsconfig you copy from an old project? The regex you always lose?

snipit stores them locally, tagged and searchable, ready to copy to your clipboard in one command. No account, no sync, no internet — just a JSON file on your machine.


Install

npm i -g @fouaden/snipit

Requirements: Node.js 18+


Note!

macOS/Linux: If you get an EACCES permission error, run

 sudo npm install -g @fouaden/snipit # This happens when npm's global folder is owned by root.

Quick Start

# save a snippet
snipit save "kill port 3000" --code "lsof -ti:3000 | xargs kill" --tag node

# find it
snipit list --tag node

# grab it
snipit get "kill port 3000" --copy

Commands

Save a snippet

# inline code
snipit save "kill port 3000" --code "lsof -ti:3000 | xargs kill" --tag node

# from a file — reads the file content and stores it
snipit save "tsconfig base" --file ./tsconfig.json --tag ts

# multiline — opens your default editor
snipit save "async fetch" --tag js

Tags are comma-separated and optional:

snipit save "docker prune" --code "docker system prune -af" --tag "docker,ops"

List snippets

snipit list                    # all snippets
snipit list --tag ts           # filter by tag
snipit list --search "docker"  # search by title

Get a snippet

snipit get "kill port 3000"          # prints to terminal
snipit get "kill port 3000" --copy   # prints + copies to clipboard

Since output goes to stdout, you can pipe it too:

snipit get "tsconfig base" > tsconfig.json
snipit get "nginx config" | ssh user@server "cat > /etc/nginx/nginx.conf"

Delete a snippet

snipit delete 3   # use the ID shown in snipit list

Data

Snippets are stored at ~/.snipit/snippets.json as a plain JSON file. No database, no server, no account.

{
  "snippets": [
    {
      "id": 1,
      "title": "kill port 3000",
      "code": "lsof -ti:3000 | xargs kill",
      "tags": ["node"],
      "created": "2026-02-25"
    }
  ],
  "lastId": 1
}

You can back it up, sync it with Dropbox, or commit it to a private repo — it's just a file.


License

MIT