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

dotfiles-pm

v0.1.1

Published

Manage your dotfiles as (un)installable, (un)linkable packages

Readme

Manage your dotfiles as (un)installable, (un)linkable packages.

Installation

Simply run:

$ npm install -g dotfiles-pm

install Install a package. Looks for a dotfile.json in PWD

uninstall <name> Uninstall a package. If it is linked, it will be unlinked.

link <name> Link one of your installed packages.

unlink <name> Unlink one of your linked packages.

Installing a package

A package is a directory containing some of your files and a dotfile.json which holds your package info. It will look something like this:

{
    "name": "nvim",
    "linkto": "/home/ben/.config",
    "withdir": "nvim",
    "ignore": [ ".git/" ]
}

| option | description | |:---: |:----| | name | our package name, for obvious reasons! | | linkto | the directory we want to link our files to. Defaults to $HOME if omitted | | withdir | an extra directory in which we want to place our actual links. So the link path becomes: linkto/withdir/somefile | |ignore | a list of files we don't want to copy when installing. You can use your usual glob patterns here, yippie!

Dotfiles copies all the files and dirs in the directory (minus the ignore list) to ~/.config/dotfiles/installed/<package name> and adds the package to its internal cache. Now we can (un)link the package, nice!

Linking a package

Simply run link to link a package.

$ dotfiles link <package name>

Uninstalling a package

Simply run uninstall to uninstall one of your packages.

$ dotfiles uninstall <package name>

Uninstalling will unlink and completely remove it from your packages directory $HOME/.config/dotfiles/installed

oh-my-zsh plugin

Place dotfiles.plugin.zsh in $HOME/.oh-my-zsh/custom/plugins/dotfiles and add it to the plugins list in your .zshrc

plugins = (dotfiles <any other stuff that was already here>)

regular zsh completion script

Place _dotfiles in a directory that is included in your zsh fpath.

e.g. $HOME/.zsh/completions would be configured like this in your .zshrc

fpath=($HOME/.zsh/completions $fpath)