Spike: Set up Sentry error monitoring for danielworkman.dev

[danworkman1]

Goal

Set up Sentry to capture client- and build-time errors on danielworkman.dev going forward, so failures surface without waiting for a visitor report.

Research findings (done before raising this)

The "how many free domains/sites" question is a non-issue — Sentry does not limit by domain or project:

• Unlimited projects on every plan, including the free Developer plan. Each site gets its own Sentry project under the same account.
• Free Developer plan limits that do apply: 1 user, 5k errors/month, 5M spans, 50 session replays, 1 uptime monitor, 1 cron monitor, ~30-day retention.
• The error quota is shared at the organization level across all projects — so danielworkman.dev and any second site would draw from the same 5k errors/month pool. For low-traffic personal sites that's plenty; a runaway error loop on one site could eat the other's quota, so set per-project rate limits/spike protection.

Conclusion: no need to choose between sites — one free account covers both, each as its own project.

Spike scope

• Create Sentry account/org (free Developer plan) and a project for danielworkman.dev
• Integrate the appropriate Sentry SDK for this site's stack; confirm source maps upload so stack traces are readable
• Gate initialization to the production hostname only (same approach as GA4 in Add GA4 (gtag.js) gated to the production hostname #16) so local/preview noise doesn't burn quota
• Configure alerting (email is fine on free tier) and spike protection / per-key rate limits
• Verify with a deliberate test error end-to-end
• Note follow-up: add second site as another project in the same org if desired

Sources

• Sentry pricing — Developer plan: 1 user, unlimited projects, 5k errors/mo
• Sentry Help: project/integration/release limits — no limit on projects