> Considering the prevalence and longevity of this error I suspect the mountain of complexity and footguns within Next.js make it impossible to track down any one cause.

Hahahaha. Anyone curious about the answer to this should go look at the source code for Next.js.