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

docker-compose-helper

v1.1.1

Published

Helper for docker-compose

Readme

Docker compose helper

Sometimes you have multiple services in your docker-compose configurations as well as multiple compose files. But for some cases you still need run only few services of many. And each time is needed to write huge command passing docker-compose files (-f docker-compose.yml -f docker-compose.dev.yml) and list of services then after command, which is exhausting and easy to make mistakes. This simple script make it a bit better experience. It analyzes compose file and provide interactive CLI to construct full command with files, services and commonly used docker-compose commands.

Demo

Installation

npm i -g docker-compose-helper

Usage

  1. Go to directory where compose file is localed
  2. Run command (currently supported commands up, down, stop, logs, build, ps, pull, rm):
    • passing it directly as argument
      ➜  my_project ✗ dch up
      Used compose files: docker-compose.develop.yml, docker-compose.test.yml, docker-compose.yml
      ? Choose service (Press <space> to select, type name to search):
      ❯◯ backend
       ◯ certbot
       ◯ client
       ◯ influxdb
       ◯ minio
       ◯ mongodb
       ◯ mqtt
       ◯ mysql
       ◯ nginx
       ◯ rabbitmq
      (Move up and down to reveal more choices)
    • select command from list (use arrows or type to search):
      ➜  my_project ✗ dch
      Used compose files: docker-compose.develop.yml, docker-compose.test.yml, docker-compose.yml
      ? command: u
      ❯ up
        build
        pull
  3. Select service (you cen type to search and use list as multi-select) and press enter to run command.

Commands arguments

Some commands already include predefined arguments to make usage more robust. (e.g. up append also --force-recreate to have new container each time you want to up it and -d not to append service output).

| command | arguments included | |-----------|--------------------| |up | -d --force-recreate| |logs | -f --tail 10 | |rm | -f -s |

Docker commands

Also it is included ability to attach to container shell using docker exec -it contaner_name bash command. In commands list there two options bash and sh.

Configuration

If you want use only some docker-compose files or set specific order, you can configure it creating .dch.json file in directory where compose files are located:

{
    "composeFiles": [
        "docker-compose.yml",
        "docker-compose.develop.yml"
    ]
}

By default script will use all yaml files found in directory which has structure like to docker-compose files (has services and version section in tpp level).