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

typescript-top-errors

v0.10.0

Published

Get the top TypeScript errors in your repository

Readme

TypeScript Top Errors

Get the top TypeScript errors in your codebase

Quick Start

Step 1

Save your TypeScript diagonistic (tsc) output in a .txt file such as ts-errors.txt

For example tsc > ts-errors.txt

Step 2

Run the CLI:

npx typescript-top-errors -inputFile=ts-errors.txt

pnpm exec typescript-top-errors

Options

-inputFile

Path to the tsc output file

-topErrors

Numbers of TypeScript errors to report (default is 10)

-topMessages

Numbers of Unique Typescript specific to your codebase to report (default is 10)

-filesCount

Number of files to display (default is 20) - pass Infinity for all files to be displayed (-filesCount=Infinity)

Programmatic use

You can also directly load the errors in a TS or Node module through exposed functions such as getTopTsErrors in parse-ts-errors

For example import { getTopTsErrors } from "typescript-top-errors/dist/parse-ts-errors"