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

robonaut

v2.2.1-alpha.0

Published

A mono-(poly)-repo manager for NPM+Git libraries.

Downloads

22

Readme

robonaut

A mono-(poly)-repo manager for NPM+Git libraries.

Demo: Youtube

Disclaimer

Warning: Robot is packed full of religious convictions that other developers may strongly disagree with.

Robonaut was haked together in 3 days, and is undoubtedly very brittle. It was designed to work with one open-source project (markserv). It is a very early tool that will likely mature alongside the code it is supporting.

About

Robonaut is designed to manage a NodeJs project that contains many repos. I found that as my project was scaling in size and complexity, I would often make stupid, simple, human errors like:

  • Forgetting to increment version numbers
  • Increment version numbers incorrectly
  • Forgetting to git push a package I had updated
  • Forgetting to npm push a package I had updated
  • Etc.

Usually this would result in a Travis build failing, followed by a frantic igging to find out why. (Hey... everything was working fine on my computer!) Clearly I needed to enlist the help of a trusty robot.

Robonaut (currently) works on a few basic principles:

  1. Modules imported must already exist as an NPM package and a GIT repo.
  2. Only one feature or patch is ever being worked on at a time. (this will change in the future)
  3. Version numbers increments are cross-linkedm (packages that are worked on simultaneously will be incremented together).

Usage

embed

robonaut embed

Embeds robonaut in your directory, by setting up a package.json and a robotnaut_modules directory.

prime

robonaut prime pkg1,pkg2,pk3

Adds an array of packages to package.json in robonautDeps.

assemble

robonaut assemble

  • Gets dependencies json from NPM
  • Git clones the dependency
  • Npm installs the repo

fuse

robonaut fuse

Cross links all dependencies with npm link.

Example:

Robonaut  🏁  LINKED...
markserv-cli ⇠ ━┓
                ┗━ ⇠ markserv-contrib-app.github
markserv-contrib-app.github ⇠ ━┓
                               ┣━ ⇠ markserv-contrib-inc.html
                               ┣━ ⇠ markserv-contrib-inc.less
                               ┣━ ⇠ markserv-contrib-inc.markdown
                               ┣━ ⇠ markserv-contrib-mod.dir
                               ┣━ ⇠ markserv-contrib-mod.file
                               ┣━ ⇠ markserv-contrib-mod.html
                               ┗━ ⇠ markserv-contrib-mod.http-404

scan

robonaut scan

Scans all modules for changed git diff.

numerate

robonaut numerate

Increments all changed packages by the same pattern in the package.json file.

Example:

  Major   Minor   Patch
 _______ _______    +
                 markserv-cli  master (1.0.61) » 1.0.62
  markserv-contrib-app.github  master (1.0.75) » 1.0.76
    markserv-contrib-inc.less  master (1.0.5) » 1.0.6
markserv-contrib-mod.http-404  master (1.0.6) » 1.0.7

transmit

robonaut transmit "My Commit message!"

Pushes code to their respective GIT repos, then publishes to the NPM repository.