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 🙏

© 2024 – Pkg Stats / Ryan Hefner

herakles

v1.2.0

Published

Slay the multi-repository monster!

Downloads

20

Readme

herakles

Slay the multi-repository monster and manage multiple repositories with a simple interface.

Managing multiple repositories is hard. Trying to stay up-to-date on all your machines is even harder. You may have tried putting your repository in your Dropbox, a different cloud provider or using BitTorrent Sync. You might have a put code in a virtual machine and then sync'ed your virtual machine across multiple machines. (I did all those things!) But there are some shortcomings with all of those and chances are your repository is already centralized on Github, Bitbucket or on your own hosted platform, so we only need sync our repositories with that centralized repository.

For anyone seeing this, this a small project for managing multiple repositories as a library and as a command-line interface. I am incubating and testing this over winter break 2015 to see if it's worth being turned into a real project or if it should stay as an experiment.

TODO:

  • [ ] Dogfood for a week
  • [ ] Unit tests
  • [ ] Scripts

Oberservations:

  • I'm not liking the tree-like structure with passing down root and name. Maybe have two with groups and repositories and repositories linking to the group. Not sure about the serialization though :/
  • Events shouldn't be static -> for 1.3.0+
  • Events should be more granular -> for 1.3.0+

If you are a fan of the monorepo approach, you might want to check out lerna.