CSP Without unsafe-inline in Astro + Vercel

How to remove unsafe-inline from your Content Security Policy in an Astro site deployed to Vercel, using SHA-256 hashes generated automatically at build time — and every pitfall we hit along the way.
page 1 of 9

How to remove unsafe-inline from your Content Security Policy in an Astro site deployed to Vercel, using SHA-256 hashes generated automatically at build time — and every pitfall we hit along the way.

A technical analysis on why US integration and the development of Puerto Ordaz represent the most important system deployment in our history.

A full account of the issues I hit upgrading a production Astro site: Svelte TypeScript preprocessing failures, transitive dependency conflicts in better-auth, and Vercel build cache pitfalls.

Chrome ships a native Summarizer API powered by on-device AI. No API keys, no server costs, no privacy concerns — the model runs entirely in your browser.

If bun run test fails with 'vitest: command not found', the fix is one word: bunx. Here's why Bun doesn't always put node_modules/.bin on PATH, and when it matters.

Unit testing Astro content collection helpers isn't obvious. Here's the exact pattern to mock getCollection and control import.meta.env.DEV so your tests actually reflect production filtering behavior.