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

wtreef

v0.1.2

Published

See where your branch changes a codebase: a treemap of the repository with the changed files lit up.

Readme

wtreef

See where a change lands in a codebase: a treemap of the repository with the changed files highlighted. Two ways to use it:

Your branch, locally. In any git checkout:

npx wtreef@latest

opens http://localhost:3753 with your current branch: everything since it left the default branch (origin/HEAD), uncommitted and untracked files included. Reload the page to see new edits. Needs git; nothing leaves your machine. npx wtreef -h lists the flags (-base, -listen, -open).

A pull request, on the web. Replace github.com with wtreef.com in a PR URL:

https://github.com/l2beat/l2beat/pull/13157
https://wtreef.com/l2beat/l2beat/pull/13157

Architecture

  • Server (cmd/, internal/): one Go binary, standard library only.

    • wtreef [directory] (local): reads the branch with git (internal/localgit) on every page load and serves it on 127.0.0.1.
    • wtreef serve (website): fetches PR metadata and changed files (GitHub GraphQL) and the head commit's tree (GitHub REST). Trees are keyed by commit SHA and cached on disk forever (size-bounded). Concurrent identical requests are coalesced.

    Both prune the tree around the changes (internal/prune) and serve it as compact JSON.

  • Client (web/): plain TypeScript, no runtime dependencies. Squarified treemap drawn on a canvas; controls and the file list are DOM. The server tells the page which mode it is in through <meta name="wtreef-mode">.

  • Contract: docs/wire-format.md.

  • npm package (npm/): a launcher plus one optional package per platform holding the prebuilt binary, as esbuild does it. npm skips an optional package it cannot fetch, so the launcher downloads a missing one from the registry and checks it against the SHA-256 recorded at build time.

Develop

npm ci            # build-time tools only (esbuild, tsc)
make dev          # website on http://127.0.0.1:8080, uses `gh auth token`
make dev-local    # this checkout on http://localhost:3753
make test check

Build for the box

make linux        # bin/wtreef-linux-amd64

Publish to npm

make npm VERSION=0.1.0     # stages bin/npm/*: wtreef and @wtreef/<platform>
make npm-publish           # platform packages first, then wtreef

Publish exactly what one make npm staged: wtreef's checksums.json pins the platform binaries of that build, and a rebuild differs (Go embeds the commit).