CI/CD

Loom’s player-build hook runs automatically in CI the same way it runs from the Unity Editor. Your pipeline needs to provide the tools the hook expects.

CI requirements

Install or cache:

• Unity 6000.3.0f1 or newer with URP 17.3.0 or newer and the modules your game needs
• Node.js 22 or 24 LTS
• npm 10 or 11
• UI node_modules

Run dependency installation before the Unity player build:

cd UI
npm ci

Use npm ci in CI so dependency resolution is repeatable.

Build flow

A typical pipeline:

1. Check out the repo.
2. Install Unity.
3. Install Node.js 22 or 24 LTS with npm 10 or 11.
4. Run npm ci in the UI directory.
5. Run the Unity player build in batchmode.
6. Archive the player output.

During step 5, Loom runs the UI production build and copies the result into StreamingAssets/Loom.

Verifying the UI build

Add a CI check that fails if the player build did not include:

Assets/StreamingAssets/Loom/index.html

Also keep the Unity log as a CI artifact. UI build failures are reported there with the npm output.

Common CI issues

• Node is installed but Unity cannot find it. Launch Unity from an environment where Node is on PATH.
• npm ci fails. Regenerate or commit the UI lockfile.
• Editor works but CI player is blank. Check whether the UI build hook ran and whether StreamingAssets/Loom was included.