Please check out the entire thread, we’ve said this is not the solution and the actual solution is being worked upon. If we have to repeat the entire discussion here, it’s just creating a duplicate, which won’t help anyone
If you’re desperate to solve this now, you can check out the workaround shared by another user:
If it’s not urgent, you can wait till we get to a long-term solution.
You can probably also downgrade Next.js to 13.2 I believe.