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

@golemio/cli

v1.12.0

Published

Collection of executables intended for use with Golemio services and modules

Readme

pipeline status coverage report

Golemio CLI

Golemio CLI is a collection of executables intended for use with Golemio services and modules

Install the CLI

Prerequisites

  • Node.js version 14 or later (https://nodejs.org)

Install locally (recommended)

$ cd my-project

# With Yarn
$ yarn add --dev @golemio/cli
# For Portman support, run yarn add --dev @apideck/portman@^1.16.1

# With npm
$ npm install --save-dev @golemio/cli
# For Portman support, run npm install --save-dev @apideck/portman@^1.16.1

# Test it out
$ yarn golemio
$ npm exec golemio

Install globally

# With Yarn
$ yarn global add @golemio/cli

# With npm
$ npm install -g @golemio/cli

# Test it out
$ golemio

Commands summary

| Command | Description | | --------------------------------------- | ----------------------------------------------------------------------------------------------------- | | golemio | Default command (welcome) | | golemio help | View available commands | | golemio migrate-db help | View available migration commands and flags | | golemio migrate-db create <name> | Create new migration scripts (--postgres, --path) | | golemio migrate-db up | Execute up migrations (--postgres, --path) | | golemio migrate-db down | Execute down migrations (--postgres, --path) | | golemio migrate-db reset | Reset all executed migrations (--postgres, --path) | | golemio import-db-data help | View available db data import commands and flags | | golemio import-db-data | Import db data (--dangerous, --postgres) | | golemio rabbitmq help | View available rabbitmq commands and flags | | golemio rabbitmq send --help | View available rabbitmq send flags | | golemio rabbitmq receive --help | View available rabbitmq receive flags | | golemio release help | View available commands | | golemio release check-modules-integrity | Check module group if new repo was added | | golemio release check | Check repos that are ready to release (--scope, --skip or --only, --interactive) | | golemio release merge | Merge repos marked as release candidate by check command (--scope, --skip or --only, --interactive) | | golemio release check-mr-pipelines | Show pipelines of merged repos (--scope, --skip or --only, --interactive) | | golemio release sync-branches | Synchronize branches after release (--scope, --skip or --only, --interactive) | | golemio release create-tags | Create tags and releases of merged repos (--scope, --skip or --only, --interactive) | | golemio release print-release-issue | Print issues and release candidate modules | | golemio swagger help | View available swagger commands and flags | | golemio swagger generate | Generate OAS file from multiple inputs | | golemio swagger api-test | Run Portman integration tests | | golemio asyncapi merge | Merge asyncapi documentation | | golemio asyncapi upload | Build and upload the asyncapi documentation to the azure blob storage |

Read release_management_CZ for more info to release command. Read migrations for more info about database migrations.

Environmental variables

| Variable | Example | Required | | ----------------------- | --------------------------------------------- | ---------------------------------------------------- | | POSTGRES_CONN | postgres://oict:oict-pass@localhost/oict-test | :white_check_mark: (mdb and idd postgres) | | RABBIT_CONN | amqp://rabbit:pass@localhost | :white_check_mark: (rmq) | | POSTGRES_MIGRATIONS_DIR | db/migrations/postgresql (default) | :negative_squared_cross_mark: | | SQL_DUMP_FILES | db/example/*.sql | :white_check_mark: (idd postgres) | | GITLAB_API_TOKEN | token | :white_check_mark: (rls) | | RELEASE_BRANCH_NAME | release | :negative_squared_cross_mark: (rls) default: release | | TARGET_BRANCH_NAME | master | :negative_squared_cross_mark: (rls) default: master |

The value of the variable GITLAB_API_TOKEN should be created in GitLab User Settings page Access Tokens. Token scopes are api, read_repository and write_repository.

Development

Local environment

To set up your local development environment, install project dependencies and create .env file in the root of the project (see .env.template for reference)

$ npm install
$ cp .env.template .env

Now you can run the CLI in development mode, just type

$ ./bin/golemio.js

You don't need to compile the source code as the script automatically registers the ts-node loader in development mode

Unit tests

Unit tests are located at test/unit. You can run them by typing

$ npm run test-unit

Integration tests

Integration tests are located at test/integration. You can run them by typing

# Run local services, recommended
$ docker-compose up -d

$ npm run test-integration

License

MIT