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

dogfen

v2026.1025.0

Published

self-rendering ~markdown~ html documents

Readme

dogfen

self-rendering ~markdown~ html documents

usage

Add the below oneliner to an existing markdown document:

<!doctype html><script type=module src=https://esm.sh/dogfen></script><textarea style=display:none>

# Header 1

## Header 2

|col 1 | col 2 |
|---|---|
|cell 1 | cell 2 |

or start writing a new one!

See a demo of (some) of the supported syntax.

Specifying Content

local file

As shown above to render a document you should prepend it with the following line, taking care to ensure the content is in the <textarea> and open in a browser:

<!doctype html><script type=module src=https://esm.sh/dogfen></script><textarea style=display:none>

If you want to modify the content using a different editor but still preview in your browser add the live attribute to the <textarea> (optionally, you can provide a value for the attribute in seconds to set the polling rate, by default it's 2.5s):

<!doctype html><script type=module src=https://esm.sh/dogfen></script><textarea style=display:none live read-only>

fetch from href

Use a query parameter to set the content with the raw text data fetched from a url:

Example: https://dogfen.dayl.in/read-only?href=https://raw.githubusercontent.com/daylinmorgan/dogfen/refs/heads/main/README.md

[!NOTE] This base url (https://dogfen.dayl.in/read-only) loads a lighter bundle (without codemirror), you could also specifying this with a query parameter (?read-only)

shareable url

It's also possible to generate shareable urls:

Example: https://dogfen.dayl.in?raw#BYUwNmD2AEDukCcwBMg

[!NOTE] This has the typical caveats of embedding data in a url, i.e. for big documents host the data at a public link and use ?href=

code

If you wish to share a code snippet rather than markdown you may use the code={lang} attribute or query parameter to treat the entire document as a code snippet

Example: https://dogfen.dayl.in/read-only?code=nim&href=https://raw.githubusercontent.com/daylinmorgan/dogfen/refs/heads/main/src/dogfen.nim

alternative versions

katex

If you need support for katex rendering append /katex to the src url to get a bundle with katex

read-only

If you are using read-only mode and won't need the editor append /read-only (or /katex/read-only) to the src url to get a bundle without codemirror

converter

You could define a shell helper function to quickly convert a markdown doc to a dogfen doc.

dogfen() {
  echo '<!doctype html><script type=module src=https://esm.sh/dogfen></script><textarea style=display:none>'
  [ -z "$1"] && cat "$1"
}
dogfen README.md > README.dogfen.html

related projects