thrive-cli v1.2.2

Install

Fresh Installation & Update to Latest

If you have not had the Thrive CLI installed to your global dependencies before you can freely install the latest release.

npm install --global thrive-cli@latest

Update or Change Version

If you already have the Thrive CLI installed you can simply re-run the global install command and specify either latest, specific release version.

npm install --global thrive-cli@{version}

Canary Releases

Everytime code is pushed to main it will be bundled and published to NPM as a canary version matching the commit short hash.

Example:

• Commit is made and has a hash of af4aaad86457527207f3a38e4eaac3de8abe7788.
• The short hash is af4aaad
• The package will be published to thrive-cli@0.0.0-af4aaad
• The package will be tagged as canary until a new commit is pushed to main and the process repeats.

The package version thrive-cli@0.0.0-af4aaad is always available to download and investigate any possible bugs or behaviours. Even after a new commit is pushed to main.

The tagged canary version only applies to the package exactly as it appears in main. You may install the canary version easily by targetting it with the install command.

npm install --global thrive-cli@canary

Setup

Once you have installed the CLI you need to create the base configuration. You can do this with the thrive init command.

thrive init

Upon completion, you should see this output.

✓ Thrive CLI config updated.

Verify

Confirm you have installed Thrive successfully by running the update command.

thrive update

# => ✓ You are using the latest version of thrive-cli

Re-running thrive init should also give you the response ⓘ Thrive CLI has already been initialized.

If you have a configuration setting that is incorrect, you can always update it using thrive config set <name> <value>. Alternatively you can re-initialize using thrive init --force to start from scratch.