When I originally built astro-strict-csp and shipped v0.2.0, my website was a pure static Astro build ( output: "static" ). Every HTML file existed on disk at the end of astro build , which meant I could enforce a strict Content Security Policy by scraping inline scripts and styles into external files and hashing them with Subresource Integrity (SRI) before deploying.
Then I migrated ezinner.com to EmDash CMS on Cloudflare Workers and D1.
Moving to a live edge CMS meant flipping Astro from Static Site Generation (SSG) to Server-Side Rendering ( output: "server" ). The moment I made that switch, my existing CSP pipeline hit an obvious wall: in SSR mode, there are no static HTML files at build time to scrape .…