Hey, you can now opt-in to our new Next.js runtime (v5) which should resolve this, when coupled with Next.js 13.5+.