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

chello

v1.0.0

Published

a hello module

Downloads

9

Readme

a node package Chello

Install

npm i chello

NOTE

published at NPM

How to Publish & Update a Package [https://www.npmjs.cn/getting-started/publishing-npm-packages/]

Publish a Package

To publish, you must be a user on the npm registry. If you aren't a user, create an account by using npm adduser

If you created a user account on the site, use npm login to access your account from your terminal.

npm login

or

npm adduser
npm whoami
npm publish

Update a Package

  1. How to Update the Version Number

When you make changes, you can update the package using

npm version <update_type>

where <update_type> is one of the semantic versioning release types, patch, minor, or major.

This command will change the version number in package.json.

note

new product first Release start with 1.0.0

patch release  increment the third digit  e.g.   1.0.1

minor release  increment the middle digit  e.g.   1.1.0

major release  increment the first digit  e.g.   2.0.0

then use npm publish Publish a Package to npm

npm publish
  1. How to Update the Read Me File

The README displayed on the site will not be updated unless a new version of your package is published, so you need to run npm version patch and npm publish to update the documentation displayed on the site.

Understanding Packages and Modules

Node.js and npm have very specific definitions of packages and modules, which are easy to mix up. We'll discuss those definitions here, make them distinct, and explain why certain default files are named the way they are.

A package is any of the following:

  1. A folder containing a program described by a package.json file.
  2. A gzipped tarball containing (a).
  3. A url that resolves to (b).
  4. A @ that is published on the registry with (c).
  5. A @ that points to (d).
  6. A that has a latest tag satisfying (e).
  7. A git url that, when cloned, results in (a).

A module is anything that can be loaded with require() in a Node.js program. The following are all examples of things that can be loaded as modules:

  • A folder with a package.json file containing a main field.
  • A folder with an index.js file in it.
  • A JavaScript file.

Most npm packages are modules