Next.js / Supabase / PostgreSQL
Production Incidents.
From a symptom to a runnable fix.
A symptom-first incident index, SQL assets and broken/fixed examples for RLS, webhook idempotency and Next.js caching.
Find the failure before the framework
The index starts with symptoms such as an empty query result, a lost server-side session or a webhook that fails after deployment. Entries lead to explanations, checklists and linked sources rather than a broad list of libraries. The repository also connects readers to relevant iloveblogs articles and the public error-explainer library.
Read both sides of the example
Three separate example directories document broken and corrected behaviour. The RLS example uses PostgreSQL and pgTAP. The webhook example uses Vitest to exercise signature verification, idempotency and retries. The Next.js example models caching and asynchronous route parameters. Each directory has its own README and runner, so readers can examine the assumptions before executing it.
Evidence beside the explanation
The value is in the relationship between the incident description, the source and the runnable example. These are educational reproductions, with their scope visible in the README. They let a reader inspect a fix instead of treating a prose recommendation as proof that it works in every application.