| name | uloop-compile |
| description | Compile the Unity project and report errors/warnings. Use after C# edits or when a full Domain Reload compile is needed. |
npx --yes uloop-cli@2.2.0 compile
Execute Unity project compilation.
Usage
npx --yes uloop-cli@2.2.0 compile [--force-recompile] [--wait-for-domain-reload]
Parameters
| Parameter | Type | Default | Description |
|---|
--force-recompile | boolean | false | Force full recompilation (triggers Domain Reload) |
--wait-for-domain-reload | boolean | false | Wait until Domain Reload completes before returning |
Global Options
| Option | Description |
|---|
--project-path <path> | Optional. Use only when the target Unity project is not the current directory. |
Examples
npx --yes uloop-cli@2.2.0 compile
npx --yes uloop-cli@2.2.0 compile --force-recompile
npx --yes uloop-cli@2.2.0 compile --force-recompile true --wait-for-domain-reload true
npx --yes uloop-cli@2.2.0 compile --force-recompile false --wait-for-domain-reload true
Output
Returns JSON:
Success: boolean
ErrorCount: number
WarningCount: number
Troubleshooting
Diagnose the failure mode before retrying.
Stale lock files (CLI hangs or shows "Unity is busy" while Unity Editor is running):
npx --yes uloop-cli@2.2.0 fix
This removes any leftover lock files (compiling.lock, domainreload.lock, serverstarting.lock) from the Unity project's Temp directory. Then retry npx --yes uloop-cli@2.2.0 compile.
Unity Editor not running (CLI returns a connection failure and no Unity process is alive):
npx --yes uloop-cli@2.2.0 launch
npx --yes uloop-cli@2.2.0 launch auto-detects the project at the current working directory and opens it in the matching Unity Editor version. After Unity finishes launching, retry npx --yes uloop-cli@2.2.0 compile.