Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JSX components require a leading newline in MDX v2 but not v1
See original GitHub issueSubject of the issue
In MDX v2 a block JSX component appears to require a newline. This is a breaking change since v1. If this is intentional it should probally be documented and this can be closed.
Your environment
N/A can be reproduced in the v2 playground https://mdx-git-next.mdx.vercel.app/playground.
Steps to reproduce
Enter the following in both the v1 https://mdxjs.com/playground and v2 https://mdx-git-next.mdx.vercel.app/playground playgrounds.
Some text...
<Box>
I'm in a box!
</Box>
Expected behaviour
Should parse in both unless this is a known breaking change in v2.
Actual behaviour
2:6: Unexpected end of file in element, expected a corresponding MDX closing tag for `<Box>` (2:1-2:6)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think that would be super useful, yeah! 💪
This is no longer an issue as it now works, it’s allowed, in the last RC (I wouldn’t recommend it though!). Please see the migration docs for guidelines on the difference between authoring in v1 and v2 though: https://v2.mdxjs.com/migrating/v2/.