Why
Inspecting JS-rendered SvelteKit app output (e.g. webapp PR previews) currently requires shelling out to a system Chrome install — `/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --headless=new --dump-dom` on macOS, nothing on Linux without an explicit install. `WebFetch` only sees the bare SPA shell because the rendering happens client-side, so we miss SSR errors, runtime registry-load failures, hydration crashes, etc. without manually launching a browser.
What
Add a chromium (or google-chrome) package to the rainix dev shell so `nix develop -c chromium --headless=new --dump-dom ` (or equivalent) works on every supported host.
Acceptance
- `nix develop -c chromium --version` works on aarch64-darwin, x86_64-darwin, x86_64-linux.
- A subsequent run against a deployed PR preview returns the rendered DOM (not just the SPA shell).
Why
Inspecting JS-rendered SvelteKit app output (e.g. webapp PR previews) currently requires shelling out to a system Chrome install — `/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --headless=new --dump-dom` on macOS, nothing on Linux without an explicit install. `WebFetch` only sees the bare SPA shell because the rendering happens client-side, so we miss SSR errors, runtime registry-load failures, hydration crashes, etc. without manually launching a browser.
What
Add a chromium (or google-chrome) package to the rainix dev shell so `nix develop -c chromium --headless=new --dump-dom ` (or equivalent) works on every supported host.
Acceptance