JS rendering for SPA pages
Last updated 2026-06-14
Definition
Many product sites are single-page apps that ship an empty shell and draw their content with JavaScript. A plain fetch reads that shell as blank. JS rendering runs the page in a headless Chromium lambda so the real content loads first, then Quri reads it. If rendering fails, it falls back to a plain fetch.
How to do this in Quri
- Start a context scan at /app/audit with your app or product URL.
- Quri detects a thin, client-rendered page and routes it to the Chromium render lambda.
- The lambda loads the page, waits for the content to draw, and returns the full markup.
- Quri extracts your product fields from the rendered page instead of an empty shell.
Frequently asked
- Why did my app site come back almost empty before?
- A plain fetch reads only the initial HTML shell a single-page app sends. The real content arrives later via JavaScript, so without rendering Quri saw a near-blank page.
- What happens if rendering fails?
- JS rendering is best-effort. If the headless browser times out or errors, Quri falls back to a plain fetch so you still get whatever the page serves, only thinner.