You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Feb 6, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run
next info
(available from version 12.0.8 and up)What version of Next.js are you using?
12.0.7 or canary
What version of Node.js are you using?
v16.13.1
What browser are you using?
Firefox
What operating system are you using?
Linux
How are you deploying your application?
testing
Describe the Bug
The documentation for custom components in MDX contains this example:
The
=
sign here may be a typo. It leads to a syntax error: unexpected token.Expected Behavior
It should not lead to a syntax error.
To Reproduce
See this code sandbox.
The text was updated successfully, but these errors were encountered: