A 500 that only happens in production, only sometimes. The culprit wasn't my code — it was the absolute build path baked into the RSC client manifest. Here's the root cause and the atomic-swap fix.
I run a small AI product on a single cheap VM, deploying it myself. One morning the homepage started throwing 500s — not always, just sometimes. The admin pages were fine. The CSS was fine. Only some routes died, and only in production.
The error in the PM2 logs was this:
Error: Could not find the module
"/tmp/riel_agent_build/src/app/page.tsx#default"
in the React Client Manifest.
A seemingly cryptic Next.js error led to a deep dive into build processes and environment variables, revealing a common pitfall…
We had one of those bugs that looked small from the outside, but exposed a much deeper architecture...
Component Architecture for React Server Components Traces the evolution from useEffect...
I lost hours debugging a Next.js 16 caching issue that had no error, no warning, and only showed up...
Reconciling the mantine-datatable supply chain breach. Why we avoided UI library bloat to build a safe, zero-dependency Next.js…
Hey devs, Every time I start a new side-project, I end up wasting the first few hours on the exact...
