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

@incremental/typescript

v0.1.5

Published

`incremental-typescript run` checks each `tsconfig.json` in the repo with `tsc --noEmit`, one task per project . Its inputs come from `tsc --listFilesOnly`, the `extends` chain, and the `package.json` files on each project's paths. Every input is hashed w

Readme

TypeScript adapter (adapters/typescript)

incremental-typescript run checks each tsconfig.json in the repo with tsc --noEmit, one task per project . Its inputs come from tsc --listFilesOnly, the extends chain, and the package.json files on each project's paths. Every input is hashed when the project is observed.

incremental-typescript run [--base REF] [--json] [--all] [--store DIR] [--root DIR] [--timeout MS]

Exit codes: 0 ok and advanced; 1 a project failed to type check; 2 usage; 4 engine error; 7 ran, baseline not advanced.

  • Full design, as built, and its gaps: spec/adapters/typescript.md.
  • Tests: make test-typescript (6 integration tests against the real engine and a scratch git repo).
  • Known cost: probes and dirs are not observed, so an edit to a file no project reads runs every project (P7 unobserved_input). This is sound. Shadow mode and a worker pool are not built.