@vercel.com is the Next JS team working on this issue: https://github.com/vercel/next.js/issues/46078? I would love to see this fixed; it's been causing us trouble for six months :C

Comments