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

editdown

v0.1.0

Published

Edit a markdown file in your browser, WYSIWYG or source, and save straight back to disk.

Readme

editdown

Edit a markdown file in your browser and save it straight back to disk.

npx editdown notes.md

editdown in action

Every other md* CLI on npm renders markdown one way: disk to browser. editdown goes both ways. You get a rich-text editor over your actual file, and Cmd+S writes it back as markdown.

Features

  • WYSIWYG editing over the real file, with a one-click toggle to raw source.
  • Cmd+S saves to disk. Writes are atomic, so an interrupted save cannot truncate your document.
  • Picks up outside edits. Change the file in your editor and the browser reloads it, keeping your scroll position. Never while you have unsaved changes.
  • Link tooltips. Hover a link to see its URL, right-click to pin, then edit or unlink it in place. Paste a URL over selected text to link it.
  • Copy rich text for pasting into Google Docs, Word, or an email client, with code blocks and lists surviving the trip.
  • Images render inline, resolved relative to the markdown file.
  • Offline and local. Binds to 127.0.0.1, no CDN, no telemetry, two dependencies.

Usage

editdown                    # edits README.md in the current directory
editdown docs/notes.md      # edits a specific file
editdown notes.md -p 3000   # pick the port (default 8432)
editdown notes.md --no-open # do not open a browser

If the port is taken, editdown walks up to the next free one.

| Shortcut | Action | |---|---| | Cmd/Ctrl+S | Save | | Cmd/Ctrl+B | Bold | | Right-click a link | Pin its tooltip | | Paste a URL over a selection | Turn the selection into a link |

Install

Nothing to install, npx editdown is the intended way to run it. If you want it always on hand:

npm install -g editdown

Requires Node 18+.

Notes

The file must already exist. editdown edits documents, it does not create them, so a typo in the filename gets you an error rather than a stray empty file.

Round-tripping runs your document through HTML and back, which normalizes formatting: list markers become -, headings become ATX (##), emphasis becomes *. The content is preserved, the exact byte-level formatting of untouched sections may not be. Keep your file in git, as you would anyway.

License

MIT