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

comment-to-fix

v0.2.1

Published

Comment to Fix — point at HTML, comment, get the fix

Readme

comment-to-fix

Point at any HTML page, leave a comment, get the fix.

comment-to-fix serves your HTML with a browser overlay that opens ready for feedback. Click any element, type a comment, and it's appended to a local inbox (.comment-to-fix/inbox.jsonl) that your coding agent reads, fixes, and marks processed — with live reload and per-comment lifecycle markers (fixing → ready).

Quick start

npx comment-to-fix ./index.html --open
pnpm dlx comment-to-fix apps/landing/index.html --root apps/landing --open
bunx comment-to-fix proposal.html --open

Defaults to ./index.html in the current directory.

Agent loop

npx comment-to-fix watch --once       # block until the next comment, print JSON
# ...implement the fix...
npx comment-to-fix mark-processed --id ann_xxx

Commands

comment-to-fix [file.html] [--root dir] [--port 5173] [--open]
comment-to-fix watch --once
comment-to-fix mark-processed --id ann_xxx
comment-to-fix help

License

MIT