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

@rayzerrek/dot-cli

v1.0.25

Published

Lightweight, cross-platform CLI manager to keep configurations (dotfiles) in sync

Readme

Dotfiles CLI (dot)

npm version npm downloads

A lightweight, high-performance, cross-platform CLI manager to keep system configurations (dotfiles) in sync across Windows, macOS, and Linux.

Installation

Via npm (Recommended)

Install the CLI globally on your system:

npm install -g @rayzerrek/dot-cli

Or run it instantly without installation using npx:

npx @rayzerrek/dot-cli status

From Source

If you prefer to clone the repository and run or link it locally:

# Clone the repository and install dependencies
git clone https://github.com/Rayzerrek/dot-cli.git
cd dot-cli
npm install

# Compile TypeScript to JavaScript
npm run build

# Link the CLI globally to your system
npm link

Configuration

The CLI supports dynamic links and custom repository locations using a config.jsonc (JSON with Comments) file.

  1. Create a configuration folder at ~/.config/dot/ (or use ~/.dotrc.jsonc in your home directory).
  2. Copy config.example.jsonc to ~/.config/dot/config.jsonc:
    cp config.example.jsonc ~/.config/dot/config.jsonc
  3. Edit ~/.config/dot/config.jsonc to define your links.

For freshly cloned dotfiles, you can also keep a portable config directly in the dotfiles repository:

git clone <your-dotfiles-repo> ~/dotfiles
dot deploy

When no global config exists, dot also looks for config.jsonc, config.json, dot.config.jsonc, or dot.config.json inside ~/dotfiles (or $DOTFILES_DIR). If that repository-local config omits dotfilesDir, the repository folder is used automatically.

Configuration Format

{
  "dotfilesDir": "~/dotfiles",
  "links": [
    {
      "name": "nvim",
      "systemPath": {
        "windows": "~/AppData/Local/nvim",
        "macos": "~/.config/nvim",
        "linux": "~/.config/nvim"
      }
    }
  ]
}
  • dotfilesDir: The absolute path to your central dotfiles repository (defaults to ~/dotfiles or DOTFILES_DIR environment variable).
  • links: An array of folders to link:
    • name: The directory name in your dotfiles repository and the label shown in the CLI.
    • systemPath: The destination path where the link should sit on the system (can be a plain string, or a platform-specific object supporting windows, macos, and linux).

Usage

# Check the state of system links and the git repository
dot status

# Create the default configuration file
dot init

# Restore or recreate missing system links 
dot link

# Copy dotfiles into their configured system locations instead of linking
dot deploy

# Use a config from a non-default cloned dotfiles directory
dot link --config ~/my-dotfiles/config.jsonc

# Stage, commit, and push changes to your dotfiles repository
dot update [optional_message]

# Display installed version
dot --version

# Display help
dot help