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

@kanztickets/common

v1.0.31

Published

1. Login to npm in command line terminal npm login

Readme

  1. Login to npm in command line terminal npm login

  2. Install package for project npm i del-cli tsc --save-dev

  3. change tsconfig.json uncomment declaration and outdir properties

  4. Create build folder mkdir build

  5. change file package.json by adding: "main": "./build/index.js" // specify file index.js for lookup when import from other file "types": "./build/index.d.ts" // this file was created when we npm run build. This file contains type of functions in index.js "files": ["build/**/"] "scripts": { "clean": "del ./build/", // to clean file "build": "npm run clean && tsc" // clean file when build again }

Flow This common module

change config in tsconfig.json to specify out dir build, and create index.d.ts for types build current source from ts to js file in /build specify index.js for the external import specify index.d.ts for type definition