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 🙏

© 2025 – Pkg Stats / Ryan Hefner

who-wrote-that

v0.1.0

Published

A command line tool to quickly lookup code owners of classes, methods and more.

Downloads

1

Readme

Who Wrote That CLI

A command line tool to quickly lookup code owners of classes, methods and more.

What you'll find in this document:

Inspiration

Starting to work on a larger software project is often intimidating. Who Wrote That makes it easy to find a person of contact that owns a specific declaration within a file. Depending on the programming language a declaration may be a function, method, class or interface declaration.

Who Wrote That works with Git repositories. It uses Tree-sitter parsers to build Abstract Syntax Trees of code written in a multitude of different programming languages.

Usage

To use Who Wrote That with your directory or file, it must be or be located within a Git repository and it must use one of the supported programming languages.

Installation

You can install Who Wrote That globally with Yarn

$ yarn global add who-wrote-that

or NPM

$ npm install -g who-wrote-that

decl

wwt decl <file> <definition>

Lookup code owners of a given declaration inside a file.

line

wwt line <file> <lineNumber>

Lookup code owners of a declaration on a given line of a file.

Options

| Option | Description | | ------ | ----------- | | -d --depth <number> | The maxmium recursive depth of the code owner algorithm (e.g. the number of commits to look back in history). Takes a positive number. Defaults to undefined -- unlimited recursive depth. | | -f --format <format> | Output format. Allowed values are pretty, data, and json. Defaults to pretty. | | -s --strategy | Strategy used for the code owner algorithm. Allowed values are weighted-lines, and lines. Defaults to weighted-lines. | | -v --version | Outputs the version number | | -h --help | Outputs usage information |

Language support

  • Go
  • Java
  • JavaScript
  • Python

Extensibility

Adding a new language

To add support for a new language

  • create a language file in src/languages;
  • and import the language file in src/languages/index.ts.

Development

Listen to changes and make them accessible through wwt from the command line:

$ yarn start

Run ESLint:

$ yarn eslint

Run TypeScript compiler checks:

$ yarn tsc

Run tests:

$ yarn test

Release

  1. Change the version in package.json and src/index.ts.
  2. Create a pull request to merge the changes into master.
  3. After the pull request was merged, create a new release listing the breaking changes and commits on master since the last release.
  4. The release workflow will publish the package to NPM.