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

flowable-cli

v3.0.1

Published

Flowable CLI

Downloads

138

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

tijs.rademakerstijs.rademakersjorge.navarrojorge.navarro

Keywords

oclif

Readme

flowable-cli

Flowable CLI

oclif Version Downloads/week

Usage

$ npm install -g flowable-cli
$ flowable COMMAND
running command...
$ flowable (--version)
flowable-cli/3.0.1 darwin-arm64 node-v22.21.1
$ flowable --help [COMMAND]
USAGE
  $ flowable COMMAND
...

Commands

flowable components build

Build custom components

USAGE
  $ flowable components build [--config <value>] [--env <value>] [-v] [--beautify]

FLAGS
  -v, --verbose   Verbose mode
      --beautify  Beautify the output (Not minifying it)

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Build custom components

flowable components create

Create a new custom component

USAGE
  $ flowable components create [--config <value>] [--env <value>]

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Create a new custom component

flowable components doctor

Check the custom components project

USAGE
  $ flowable components doctor [--config <value>] [--env <value>]

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Check the custom components project

flowable components init

Initialize a repository for custom components

USAGE
  $ flowable components init [--config <value>] [--env <value>] [-b] [-n <value>]

FLAGS
  -b, --onlyBoilerplate
  -n, --name=<value>

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Initialize a repository for custom components

flowable components types

Generate typescript types for a custom component properties

USAGE
  $ flowable components types [--config <value>] [--env <value>]

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Generate typescript types for a custom component properties

flowable components upload

Upload the custom components

USAGE
  $ flowable components upload [--config <value>] [--env <value>] [--build-dir <value>] [--draft | --minor | --major |
    --patch | --version <value>]

FLAGS
  --build-dir=<value>  Path to the build directory
  --draft              Upload the components to draft, you can install it later. This prevents non developers from
                       seeing the new version at Design
  --major              Increment major version
  --minor              Increment minor version
  --patch              Increment patch version
  --version=<value>    Version to upload (e.g. 1.0.0)

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Upload the custom components

flowable components watch

Start a developing server

USAGE
  $ flowable components watch [--config <value>] [--env <value>] [--ignore-config] [-v]

FLAGS
  -v, --verbose        Verbose mode
      --ignore-config  Ignore project configuration

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Start a developing server

flowable deploy

You can deploy an app zip file or a build output from a custom components library

USAGE
  $ flowable deploy -i <value> [--config <value>] [--env <value>]

FLAGS
  -i, --input=<value>  (required) [default: ./dist] Input app zip file path or a build directory path

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  You can deploy an app zip file or a build output from a custom components library

  Deploy an app to Work

flowable environment add

Add or update an environment configuration

USAGE
  $ flowable environment add -n <value> -t design|work -b <value> -p <value> [--config <value>] [--env <value>]

FLAGS
  -b, --baseUrl=<value>  (required) Base URL for the environment
  -n, --name=<value>     (required) Unique name for the environment
  -p, --token=<value>    (required) Access token for the environment
  -t, --type=<option>    (required) Type of the environment
                         <options: design|work>

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Add or update an environment configuration

flowable environment delete

Delete an environment configuration

USAGE
  $ flowable environment delete [--config <value>] [--env <value>] [-n <value>] [-a]

FLAGS
  -a, --all           Delete all environments
  -n, --name=<value>  Unique name for the environment

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Delete an environment configuration

flowable environment get

Get an environment configuration

USAGE
  $ flowable environment get -n <value> [--config <value>] [--env <value>]

FLAGS
  -n, --name=<value>  (required) Unique name for the environment

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Get an environment configuration

flowable environment list

List the available environments

USAGE
  $ flowable environment list [--config <value>] [--env <value>]

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  List the available environments

flowable export

Export an app from Design

USAGE
  $ flowable export [--config <value>] [--env <value>] [-l <value> | -a <value> | -w <value>] [-o <value>]

FLAGS
  -a, --app=<value>        App key
  -l, --library=<value>    Custom component library key. It will export the In-App Library app
  -o, --output=<value>     [default: Your current working directory] Output directory
  -w, --workspace=<value>  Workspace key

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Export an app from Design

flowable import

Import an app to Design

USAGE
  $ flowable import -i <value> -w <value> [--config <value>] [--env <value>] [-o | -k]

FLAGS
  -i, --input=<value>      (required) Input app zip file path
  -k, --keepBoth           Keep both the old and new app
  -o, --override           Override the app if it already exists
  -w, --workspace=<value>  (required) Workspace key

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Import an app to Design

flowable login

Authenticate with Flowable

USAGE
  $ flowable login [--config <value>] [--env <value>] [--skipDesignLogin] [--skipArtifactoryLogin]

FLAGS
  --skipArtifactoryLogin  Skip login to Flowable Artifactory. Skip it if you want to use your own npm registry
  --skipDesignLogin       Skip login to Flowable Design. To only login to artifactory

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Authenticate with Flowable

flowable ping

Check the connection with the Flowable services

USAGE
  $ flowable ping [--config <value>] [--env <value>]

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Check the connection with the Flowable services

flowable publish

Publish an app from Design to Work

USAGE
  $ flowable publish [--config <value>] [--env <value>] [-l <value> | -a <value> | -w <value>] [-t <value>]

FLAGS
  -a, --app=<value>         App key
  -l, --library=<value>     Custom component library key. It will publish the In-App Library app
  -t, --targetName=<value>  [default: _default] Work target environment name. Example: production
  -w, --workspace=<value>   Workspace key

COMMON FLAGS
  --config=<value>  [default: ~/.flowable/cli-config.yml] Path to the config file
  --env=<value>     Environment name, if not provided, the selected environment will be used

DESCRIPTION
  Publish an app from Design to Work

flowable components create

Create a new custom component

USAGE
  $ flowable components create

DESCRIPTION
  Create a new custom component

flowable components init

Initialize a repository for custom components

USAGE
  $ flowable components init [-b]

FLAGS
  -b, --onlyBoilerplate

DESCRIPTION
  Initialize a repository for custom components

flowable components migrate

Migrate a custom component from a legacy project

USAGE
  $ flowable components migrate

DESCRIPTION
  Migrate a custom component from a legacy project

flowable components register-interactive

[Advanced] Register project and/or custom components that already exists

USAGE
  $ flowable components register-interactive

DESCRIPTION
  [Advanced] Register project and/or custom components that already exists

flowable components upload

Build and upload the custom components

USAGE
  $ flowable components upload [-v]

FLAGS
  -v, --verbose

DESCRIPTION
  Build and upload the custom components

flowable components watch

Start a developing server

USAGE
  $ flowable components watch

DESCRIPTION
  Start a developing server

flowable login

Authenticate with Flowable

USAGE
  $ flowable login

DESCRIPTION
  Authenticate with Flowable

ALIASES
  $ flowable login

flowable login login

Authenticate with Flowable

USAGE
  $ flowable login login

DESCRIPTION
  Authenticate with Flowable

ALIASES
  $ flowable login