We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See related issue: vercel/next.js#26130
It's supposedly fixed in the canary branch, but I will wait until 11.0.1 is out before trying to patch things up.
Posting this in case anyone is getting upgrade problems..
The text was updated successfully, but these errors were encountered:
The bug has fixed in the next version
vercel/next.js#26281
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
See related issue: vercel/next.js#26130
It's supposedly fixed in the canary branch, but I will wait until 11.0.1 is out before trying to patch things up.
Posting this in case anyone is getting upgrade problems..
The text was updated successfully, but these errors were encountered: