Damn. If this is a Next.js issue then I'm pretty disappointed that it doesn't work well for such a common use case.

From the looks of that issue there are workarounds in some instances though.