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

@open-condo/migrator

v1.0.1

Published

CLI util to run code and infrastructure migrations for condo-based applications

Readme

@open-condo/migrator NPM

CLI util to run code and infrastructure migrations for condo-based applications.

NOTE: The documentation below describes how to use these package, but does not describe which migrations you need to run and why. For this information, go to our Migration Guides.

Table of contents

Local usage

You can use package in your condo monorepo fork by running the following command to build package:

yarn workspace @open-condo/migrator build

And then the one to run it:

npx @open-condo/migrator --help

Remote usage

Without installation

You can use migrator on remote instances without installing additional packages by running:

npx @open-condo/migrator@latest --help

With installation

Or alternatively you can install it with:

yarn add -D @open-condo/migrator

And then run with:

npx @open-condo/migrator --help

How to run migration commands

List of commands and arguments

You can use the following command to explore list of all available commands:

npx @open-condo/migrator --help

Then you can explore command arguments / description by running the following:

npx @open-condo/migrator <command> --help

Running command locally

You can migrate whole monorepo by running command from monorepo root. For example:

npx @open-condo/migrator add-apps-kv-prefixes

Or you can more precisely run it for single / multiple apps:

npx @open-condo/migrator add-apps-kv-prefixes -f condo address-service

Running command on remote environments

You can also run migration commands on deployed applications where access .env files is not possible, since environment variables are passed from external tools and apps are deployed "one per pod".

For this scenarios you can migrate single app at a time by running commands like this:

REDIS_URL=redis://remote_user:*******@127.0.0.1:6379/6 npx @open-condo/migrator add-apps-kv-prefixes -f condo

NOTE: You can remove REDIS_URL=** part if environment variables are already set (from export or other external tool)

You can also run migrator from specific app folder instead of using --filter arg:

cd apps/condo
npx @open-condo/migrator add-apps-kv-prefixes

Available commands

add-apps-kv-prefixes

This command will add keyPrefix to all your keys of your KV database (Redis).

For example, for condo app new keys will look like this:

  • my_key -> condo:my_key
  • sess:asd123ghj -> condo:sess:asd123ghj
  • bull:low:importMeters:123 -> {condo:bull:low}:importMeters:123

You can read more about our motivation and key format in our Migration Guides