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

@monopolycli/monopoly

v2.0.1

Published

Autocode's polyrepo orchestrator.

Downloads

5

Readme

monopoly

Autocode's polyrepo orchestrator.

Getting started

You'll need the AWS CLI installed, start by following this guide.

Run aws configure to setup your credentials.

Then:

git clone [email protected]:autocode/monopoly
cd monopoly
node src clone
node src install
node src secrets sync

This will:

  1. Clone all the repositories you need to your local machine under ./monopoly/repos.
  2. Install all dependencies for each cloned repository.
  3. Download secrets for each target environment for each service to ./envfiles

Now open up ./services.json. Anything set to local is going to be started locally when you run npm run dev. For anything set to staging, all the services running locally are going to be configured to point to the staging instance of that service.

If you look at ./targets.json, it contains all the configuration settings for each service. These key-value pairs override any environment variables for services running locally, this lets us control which deployment (local/staging/prod) of a service our local services talk to.

Does it look ugly?

If the colors look wonky, you might need to enable 256-bit color in your terminal.