mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-10-30 09:16:55 +00:00
Miguel Ángel
9e5da67409
* fix(cli): a Chrome that fails to start says how it ended, and a slow start says so A failed launch only reported "Protocol error (Target.setDiscoverTargets): Target closed". It now runs the browser once more on its own with the same flags and reports its exit code (Windows codes named: missing runtime, out of memory, security software), its last stderr lines, or that it stayed up. The CLI and the engine's render launch both use it. A start slower than 5 s prints "Chrome is still starting...", and a --timeout that looks like seconds says it is milliseconds. * chore(cli): cut the Chrome launch diagnosis comments to the comment limit * fix(cli): the Chrome startup check runs Chrome as puppeteer does and can be cancelled The check started the browser with only the caller's flags, so a full Chrome ran headful and was blamed for a missing X server. It now uses puppeteer's default arguments (headless included). The check is stopped when the CLI is stopped, and the GPU probe, whose failure falls back to software anyway, skips it. * fix(cli): a Chrome launch error is never replaced by a failure to explain it The startup diagnosis asks puppeteer for its default arguments before re-running Chrome. If that call fails, its error used to replace the launch error the caller needed. The launch error is now reported as it was. The core package size budget rises to cover the new chromeStartup module (about 4.7 KB unpacked). * refactor(engine): the Chrome startup diagnosis lives in the engine, not core Both callers launch Chrome through the engine (the CLI already imports it), so the engine owns the diagnosis. Core's package size budget is back to its old value.