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

npm-module-tuto

v1.1.0

Published

- Build with TypeScript - Using ES Moudles (but also compatible with CommonJS) - That can be used in JavaScript AND TypeScript projects - That can be used in web or node environement

Readme

How to setup an NPM package ?

  • Build with TypeScript
  • Using ES Moudles (but also compatible with CommonJS)
  • That can be used in JavaScript AND TypeScript projects
  • That can be used in web or node environement

/!\ This package config will not fully work in a CommonJS modules /!\

1/ Init NPM package

    $ yarn init

Then fill all fields (you can use default values for instance)

Install dependencies for typescript

    $ yarn add -D typescript tsc @types/node

3/ Add tsconfig.json

    {
        "compilerOptions": {
            "module": "node16",             // Type of modules to use (also see moduleResolution)
            "target": "esnext",             // Version of the transpilled JS
            "noImplicitAny": true,
            "removeComments": true,
            "preserveConstEnums": true,
            "outDir": "./dist",             // Folder for transpilled files (.js and .d.ts)
            "rootDir": "./src",             // Folder with source files
            "declaration": true,            // Create .d.ts files for 'types'
            "declarationMap": true,         // 
            "moduleResolution": "node16",   // !important if you want to be able to use JS out with ES modules
        },

        "include": [
            "src/**/*"
        ],
        "exclude": [
            "node_modules"
        ]
    }

4/ Edit the package.json

Config package entries and type

    ...
    "type": "module",               // You want to use ES modules
    "types": "./dist/index.d.ts",   // Entries for Ts types
    "main": "./dist/index.js",      // Entries for Js usage
    ...

Add build script

    "scripts": {
        "build": "tsc"              // tsc will transpile the source files into .js and .d.ts files
    },

5/ Add .gitignore and .npmignore files

/!\ It's importante to add the .npmignore event if you leave it empty as we will ignore the dist/folder in the github repo but we want to include it in the NPM Package. In a way the .npmignorewill overwrite the.gitignorefornpm`. /!\

.gitingore

    node_modules/
    dist/
    yarn.lock

.npmignore

    yarn.lock
    src/

Add the src/folder if you don't want to publish the source files on npm