Results 1 comments of sagshar5

Thank you for rtpascual for identifying this As this is identified as an issue for Next.JS version as mentioned in already closed issue here https://github.com/vercel/next.js/issues/63623, I am marking this issue...