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

incdepnpmpublish

v1.0.12

Published

Increment dependency and publish

Downloads

10

Readme

NPM PUBLISH package needed to replace standard npm publish command with autoreplace of injected aliases

It's extends base functionality by nex features:

  • publishing dependency package that placed near to current package
  • autoincrement version dependency version
  • find and replace [depPath]/[pathToReplace]/.injected path to main [mainPath]/platform
  • publishing dependency to npm
  • increment dependency version in main package
  • increment main package version
  • publishing next main package version on npm

Usage:

in package.json of main package you need to add next command to scripts:

"publishNext": "node ../scripts/publishMain/index.js --mainPath=../mobile --depPath=../common --depName=commonnpmpublish"

then you can run it by command:

npm run publishNext -- --mainVersion=1.1.1 --depVersion=0.0.2

There several arguments:

  • mainPath - path to main package itself
  • depPath - path to dependency package
  • depName - name of dependency on npm (needed to update version of dependencies of main package)
  • mainVersion - forced version of main package for cases when you do not know is it free next version
  • depVersion - forced version of dependency package for cases when you do not know is it free next version