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

@tanishqkancharla/npm-boilerplate

v0.0.1

Published

A boilerplate for typescript npm packages

Readme

npm-ts-boilerplate

A boilerplate for typescript packages for npm. Esbuild, Api Extractor, Vitest.

# Build into dist folder
npm run build

# Check types and api-extractor
npm run check

npm run test

# Build and publish to NPM (make sure the version is bumped)
npm run release

# Print the bundlesize of the minified package and exit
npm run bundlesize

I've been iterating on this for a while. Here are the interesting bits:

  • Packages are bundled into index.cjs (for CommonJS) and index.js (for ESM).
  • Types are all bundled into index.d.ts
  • Sourcemaps for bundles point to src directory. One could argue the bundles are readable by themselves (since they're not minified), but the source map files are small, and reading in Typescript vs. Javascript can help debug (you know the type of each variable).
  • Only src and dist folders are published to NPM.
  • Tests are in *.test.ts files, run by Vitest
  • API Extractor checks for you that everything you meant to export is exported and everything that was not meant to be exported isn't.

The reason I don't just use Parcel (my preferred build system) is because of:

  • https://github.com/parcel-bundler/parcel/issues/7951
  • Couldn't find a great way to integrate API extractor
  • Parcel mangles names, and I didn't know how to turn that off.