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

image-diff-cli

v0.0.3

Published

Fast screenshot versioning and visual diffs for UI work. 📸

Readme

image-diff-cli

Fast screenshot versioning and visual diffs for UI work. 📸

image-diff-cli watches a folder for new screenshots, auto-versions each capture, and lets you compare the latest changes instantly.

Why it helps

  • No manual renaming: screenshots become session_V1, session_V2, ...
  • Immediate visual history: side-by-side output is rebuilt automatically
  • Quick diff inspection: open horizontal or vertical slider views from the keyboard
  • Great for rapid UI iteration loops

Quick start ⚡

Run directly with npx:

npx image-diff-cli

Typical run for Desktop screenshots:

npx image-diff-cli -d ~/Desktop

Browser viewer mode (auto-updating):

npx image-diff-cli -d ~/Desktop --web

What happens next:

  1. New screenshots (.png, .jpg, .jpeg) are detected
  2. Files are moved into your session output folder
  3. Versioned files are saved as <session>_V{n}.png
  4. <session>_iterations.png is regenerated
  5. You can open diff views with keyboard shortcuts

Command options ⚙️

  • -d, --dir <path>: directory to watch (default: .)
  • -o, --output <path>: output root directory (default: ./output)
  • -n, --name <sessionName>: session name for folder/files (prompts if omitted in interactive mode)
  • --on-exists <policy>: behavior when session directory exists (prompt, fail, reuse, increment)
  • --no-interactive: disable prompts and key controls
  • --web: start local browser viewer with live updates
  • --web-port <port>: browser viewer port (default: 4738)
  • --debug: print startup/debug information
  • -h, --help: show help

Live web viewer

When --web is enabled, the CLI starts a local viewer (for example http://127.0.0.1:4738) and opens it in your browser.

  • Horizontal mode: compares latest 2 screenshots
  • Vertical mode: compares latest 2 screenshots
  • Pixel diff mode: highlights changed pixels between latest 2 screenshots
  • Side-by-side mode: shows all screenshots in the session (horizontal scroll)
  • New screenshots appear automatically without manual reload

Interactive keys ⌨️

  • h: open horizontal slider diff (last 2 images)
  • v: open vertical slider diff (last 2 images)
  • p: generate and open pixel diff image (last 2 images)
  • b: open side-by-side image (<session>_iterations.png)
  • q or Ctrl+C: quit

Typical workflow

  1. Start one session per task or feature (-n checkout, -n auth, etc.)
  2. Make a UI change
  3. Take a screenshot
  4. Press h/v/p/b to inspect changes
  5. Repeat until done

Notes

  • Built for local development, not CI image regression baselining
  • Most useful when screenshots are captured with a consistent viewport/area