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

jancedemo

v1.0.0

Published

start my first open source

Readme

Create First Open Source JavaScript Library

following by How to Write an Open Source JavaScript Library

configuring npm

  • npm set init-author-name 'janceChun'
  • npm set init-author-url 'https://jancechun.github.io/janceChun/'
  • npm set init-license 'MIT'
  • npm set save-exac true
  • cat ~/.npmrc
  • npm adduser
  • npm init

publish git

  • git add -A
  • git commit -m 'add init'
  • git push

publish npm

  • npm pubslih
  • npm info

git tag

  • git tag 0.0.1
  • git push --tags

publish beta version

  • git tag 0.1.0-beta.0
  • git push
  • git push --tags
  • npm publish --tag beta
  • npm info
  • npm dist-tag ls ( u can run git tag 0.1.0-beta.1 and then git push --tags && npm publish --tag beta to update the npm tag packe. the customer can npm install janceDemo@beta to update beta package )

setting

  • npm i -D mocha chai

releases with semantic-release

  • npm install -g semantinc-release-cli
  • semantic-release-cli setup
  • add .travis.yml
before_script:
  - npm prune
script:
  - npm run test
after_success:
  - npm run semantic-release

writing conventional commits with commitizen

  • npm install -D commitizen cz-conventional-changelog
  • add package.json
 "scripts": {
    "commit":"git-cz",
    "test": "mocha src/index.test.js -w",
    "semantic-release": "semantic-release pre && npm publish && semantic-release post"
  },
   "czConfig":{
      "path":"node_modules/cz-conventional-changelog"
   }
     
  • git add -A
  • npm run commit

commiting a new feature width commitizen

  • npm run commit
? Select the type of change that you're committing: feat:     A new feature
? Denote the scope of this change ($location, $browser, $compile, etc.):
 random
? Write a short, imperative tense description of the change:
 add avility to get an array of names
? Provide a longer description of the change:
 if you pass a number to the random function . you will receive an array with the number of randomw
item
? List any breaking changes:
 close #2

Automatically releasing with TravisCI

Automatically running test before commits with ghooks

Adding code code coverage recording with Istanbul