Hosanna Compiler License And Tool Setup

The same Hosanna license key authorizes the compiler and the framework source artifacts included by its entitlements.

Install the Declared SDK and Compiler

Read the project versions from hosanna.json, then install them through the locked project copy of Hosanna Tools:

npm ci
npx hst compiler:install
npx hst sdk:install
npx hst compiler:status

compiler:install reads the compiler version from hosanna.json, downloads the matching release, and installs it as ./bin/hsc for the app. This keeps local development and CI on the same compiler version.

Licensing

If the compiler reports that this machine is not activated:

1. Print the machine fingerprint:

   ./bin/hsc --fingerprint

2. Submit the fingerprint and your work email through the Hosanna activation form. Do not submit the license key in the form.

3. Provide the issued key without echoing it:

read -rsp 'Hosanna license: ' HSC_LICENSE_KEY
echo
export HSC_LICENSE_KEY
npx hst license:status

For CI, store HSC_LICENSE_KEY as a masked secret and expose it only to install/build steps. Never commit license.key, put the value in build config, or print it.

Build and Diagnose

Use HST for normal builds:

npx hst build roku dev device

Run the app-local compiler directly only for compiler diagnostics:

./bin/hsc --help

Application scripts should wrap commands that actually exist in that application. The current sample repository includes:

"roku:build:dev": "npx hst build roku dev device",
"roku:build:prod": "npx hst build roku prod device --hsc-project platforms/hsconfig-roku.prod.json"

Do not copy an example package script until the referenced files and options exist in your repository.

Source Install Safety

npx hst sdk:install refuses to discard modified SDK content. Use npx hst config source to inspect the current source mode. Embedded and shared local modes are development conveniences; never commit a local path, symlink, downloaded source tree, or license secret in place of the production hosanna.json pin.