fix: activate defaulted to a build target platform, and errors printed as {}

[frostebite]

Found and fixed while investigating why unity-activate#111's thin-wrapper CI was failing on every job.

Two real bugs

1. activate inherited a build-oriented targetPlatform default.

ActivateCommand.configureOptions() calls UnityOptions.configure(), which defaults targetPlatform to StandaloneWindows64 — a sensible default for build, meaningless for activate (which doesn't build anything, just needs an editor image to run activation inside). A bare game-ci activate <path> — exactly what unity-activate's thin wrapper calls, with no --target-platform flag — hit RunnerImageTag's Windows/il2cpp version gate and threw:

Windows-based builds are only supported on 2019.3.X+ versions of Unity.

...for any older Unity version, on every host. NoTarget already exists and maps to the generic image, skipping that check entirely — it's what unity-engine-core's extracted activate logic uses for exactly this case. activate now defaults to it; an explicit --target-platform still overrides.

2. log.error() printed [ERROR] {} for any bare Error.

This is what made bug #1 nearly impossible to see from CI logs. inspect()'s fallback for non-string values is JSON.stringify(value) — but Error's message/stack/name are non-enumerable own properties, so JSON.stringify(new Error('anything')) is always '{}'. Every uncaught error in the CLI — not just this one — was printing as a useless empty object. Error instances are now special-cased to print their stack.

How I found it

Reproduced locally: bun run src/index.ts activate <path-to-a-fake-2019.2.14f1-project> on a fresh git repo reproduced the exact [ERROR] {} from CI. Fixing bug #2 first turned that into the real message (bug #1), which then explained every failing job in unity-activate#111 (all older Unity versions — the "Tests" job, which doesn't shell out to a real Unity version, was the only one that passed).

Testing

• New test: activate-command.test.ts — configureOptions() defaults targetPlatform to NoTarget, and still honors an explicit --target-platform.
• New test: logger/index.test.ts — log.error(new Error(...)) prints the message, not {}.
• bun run test — 147 pass, 3 skip, 0 fail (144 pass, 3 skip before this PR — 3 new tests, no regressions).
• Manually verified locally past both bugs: activate now reaches the real docker run invocation (fails only because Docker isn't installed in my sandbox, which is expected).

🤖 Generated with Claude Code

[coderabbitai]

Important

Review available on request

• 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 564a4e7c-3da9-4c18-a206-edc5026405dd

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}