Skip to content
Discussion options

You must be logged in to vote

Hi, this check was changed in v9.3.1-canary.0 of Next.js. Can you check if you are you still seeing this error on that version?

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@sdornan
Comment options

Answer selected by sdornan
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
3 participants