React (future example)

A dedicated React sample repo (Next.js, Remix, or Vite + API) is not part of this documentation site yet. The patterns match Astro (SSR): run HMAC signing only on the server or in build CI, and pass fully signed src strings into the tree as props or loader data.

Planned stack (sketch)

Stack	Where signing runs	Client receives
Next.js (App Router)	Server Components, Route Handlers, or (Pages Router) getServerSideProps	Image URL strings only
Remix	loader / action on the server	JSON with signed URLs
Vite + SPA	Separate Node/serverless API, or add SSR if you need render-time sign	Never the HMAC secret

How this example will differ from Astro

• Routing — app/page.tsx and loaders vs .astro frontmatter and getStaticPaths.
• Env — Next.js: server-only modules and server env (not NEXT_PUBLIC_* for secrets). Vite SPA: only a BFF or build step signs.
• Images — Next.js <Image> needs remotePatterns (or equivalent) for your Rendorix host; align width/height with presets.

Checklist before publishing a React example

• signUrl matches production edge behavior (shared test vectors with the Rendorix stack).
• No HMAC secret in the client bundle (grep RENDORIX_HMAC in dist / .next output).
• Documented base URL and env per environment.
• Short README in the sample repo: how to run the API that signs, how to run the app.

Related reading

• Usage: Generating image URLs
• Rendering strategies
• Security

When a public repo exists, this page can gain clone instructions and a link to a Network-tab screenshot of a 200 from your img.* host.