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 🙏

© 2025 – Pkg Stats / Ryan Hefner

creating-node-modules

v1.0.8

Published

In this tutorial we will learn how to create our own node module.

Readme

#Creating Node Modules

  1. Create a package.json file

    $ npm init

  2. Automated response ask you questions to build the package.json file. ex: First it asks for a name, then version number, decription etc. Some fields have a default, others can be left blank.

  3. Next create an index.js file. In that file, add a function as a property of the exports object. This will make the function available to other code.

    // My module
     exports.printMsg = function() {  
       console.log("This message is from the npm-demo-pkg");  
    }  
    

#Publishing Node Modules

  1. You can publish packages that are not node modules. In fact, any files that are buddled together with a package.json file can be handled as a module.

  2. The two required fields are the name and the version.

  3. Create a user with the npm registry.

    $ npm adduser

    ls will can show you the information that is stored locally for your user. You can also test that your new user has been created by going to: npmjs.org/~

  4. Finally publish the node module.

    $ npm publish