CLI / Configuration

Configuration

Inspect and set the defaults the BornEngine CLI uses for new projects.

Use the configuration group to make project creation predictable across shells:

shell

bornengine config set package-manager pnpm
bornengine config get package-manager
bornengine config list

config set <key> <value> writes a value, config get <key> reads one key, and config list prints the known configuration. These defaults are used by interactive scaffolding; explicit command flags take precedence.

The top-level update command is related to releases, not project configuration:

shell

bornengine update

It checks for a newer CLI release and prints the command needed to install it. It does not self-update. Use bornengine upgrade [version] when you want the CLI upgrade flow.

Command reference

Check for CLI updates

Check the release channel without silently replacing the CLI.

bornengine update

Options

-v, --verbose (repeatable)

Behavior

Checks for a newer CLI release and prints the installation command. It does not self-update the binary.

Examples

bornengine update

Set a CLI configuration value

Persist a named BornEngine CLI configuration value.

bornengine config set <key> <value>

Options

<key> is the configuration name
<value> is stored as the selected value
-v, --verbose (repeatable)

Behavior

Writes a configuration value used by subsequent CLI operations.

Examples

bornengine config set package-manager pnpm

Read a CLI configuration value

Print the current value for one configuration key.

bornengine config get <key>

Options

<key> is the configuration name
-v, --verbose (repeatable)

Behavior

Reads one configuration key without changing it.

Examples

bornengine config get package-manager

List CLI configuration

Print the configuration values currently known to the CLI.

bornengine config list

Options

-v, --verbose (repeatable)

Behavior

Lists configuration keys and values to make project setup easier to inspect.

Examples

bornengine config list

Edit this page ↗