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

distilly

v0.1.0

Published

Distill HTML into clean, token-efficient markdown for agents. Pure, local, no network. Engine vendored and decoupled from wevm/curl.md.

Readme

distilly

Distill HTML into clean, token-efficient markdown for agents. Pure, local, no network by default.

Install

npm install distilly

Usage

The main entry point is pure: you hand it HTML you already have, and it returns markdown. It performs no network I/O.

import {htmlToMarkdown} from 'distilly';

const {markdown, truncated} = await htmlToMarkdown(html, {
	baseUrl: 'https://example.com/page', // resolve relative links/images
	size: 'm', // 's' | 'm' | 'l' (~5k / 10k / 25k chars) or 'f' (full, default)
});

size bounds the output to a char budget; truncated is true only when the budget actually cut content. Per-site extraction Profiles are auto-detected from the HTML, or you can pass one explicitly via rules to override detection.

Networked usage (injected fetch)

Optional URL fetching lives behind a separate entrypoint and requires you to inject your own fetch. No fetch is baked in: omit it and the call throws before any I/O, so a consumer can prove distilly has no egress of its own.

import {urlToMarkdown} from 'distilly/fetch';

const {markdown, truncated} = await urlToMarkdown('https://example.com/page', {
	fetch, // REQUIRED: the only transport distilly ever uses
	size: 'm',
});

The bundled URL-rewriter rules (e.g. GitHub blob → raw, MDN) clean known sources before conversion. Pass your own rules array to override or extend them, or [] to disable rewriting.

Why

distilly converts HTML to markdown locally with no baked-in network access. The core is pure; the only way it reaches the network is through a fetch you inject yourself, behind the distilly/fetch entrypoint.

License

MIT. Portions are derived from wevm/curl.md (MIT); see NOTICE and docs/VENDORING.md.