Hey @fleur,
you can now opt-in to the new version of our Next.js runtime (v5) - see details here. This version now fully supports Next 13.5+, and shouldn’t have this issue.
Hey @fleur,
you can now opt-in to the new version of our Next.js runtime (v5) - see details here. This version now fully supports Next 13.5+, and shouldn’t have this issue.