Lukasz Ladecki

I can confirm that the issue also exists in Next.js stable release (12.2.4).

Hi, so is it already implemented?

Same story here, any news about the issue?