Results 2 comments of Jaival Saija

I am facing the same issue in Next.js 14.0.3. Is this issue in the package or Next.js??