Skip to content
Discussion options

You must be logged in to vote

Hi, it sounds like you are running into this issue which is fixed in the latest canary of Next.js v9.5.2-canary.13. Please try upgrading to that version and let us know whether you are still experiencing that behavior or not

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by hk86
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants