
Security News
Axios Supply Chain Attack Reaches OpenAI macOS Signing Pipeline, Forces Certificate Rotation
OpenAI rotated macOS signing certificates after a malicious Axios package reached its CI pipeline in a broader software supply chain attack.
flowable-cli
Advanced tools
Flowable CLI
$ 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
...
flowable components buildflowable components createflowable components doctorflowable components initflowable components typesflowable components uploadflowable components watchflowable deployflowable environment addflowable environment deleteflowable environment getflowable environment listflowable exportflowable importflowable loginflowable pingflowable publishflowable components buildBuild 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 createCreate 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 doctorCheck 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 initInitialize 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 typesGenerate 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 uploadUpload 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 watchStart 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 deployYou 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 addAdd 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 deleteDelete 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 getGet 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 listList 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 exportExport 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 importImport 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 loginAuthenticate 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 pingCheck 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 publishPublish 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 createflowable components initflowable components migrateflowable components register-interactiveflowable components uploadflowable components watchflowable loginflowable login loginflowable pingflowable ping pingflowable components createCreate a new custom component
USAGE
$ flowable components create
DESCRIPTION
Create a new custom component
flowable components initInitialize a repository for custom components
USAGE
$ flowable components init [-b]
FLAGS
-b, --onlyBoilerplate
DESCRIPTION
Initialize a repository for custom components
flowable components migrateMigrate 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 uploadBuild and upload the custom components
USAGE
$ flowable components upload [-v]
FLAGS
-v, --verbose
DESCRIPTION
Build and upload the custom components
flowable components watchStart a developing server
USAGE
$ flowable components watch
DESCRIPTION
Start a developing server
flowable loginAuthenticate with Flowable
USAGE
$ flowable login
DESCRIPTION
Authenticate with Flowable
ALIASES
$ flowable login
flowable login loginAuthenticate with Flowable
USAGE
$ flowable login login
DESCRIPTION
Authenticate with Flowable
ALIASES
$ flowable login
FAQs
Flowable CLI
The npm package flowable-cli receives a total of 23 weekly downloads. As such, flowable-cli popularity was classified as not popular.
We found that flowable-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
OpenAI rotated macOS signing certificates after a malicious Axios package reached its CI pipeline in a broader software supply chain attack.

Security News
Open source is under attack because of how much value it creates. It has been the foundation of every major software innovation for the last three decades. This is not the time to walk away from it.

Security News
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.