Titus

If you have a problem with an AST, this is not the place to report it. This spec does not define ASTs.

I think this is a problem in your AST, and unrelated to this specification. a) I believe the tool generating the AST should remove the whitespace: the `text` should be...

Comments are not part of a spec; this project doesn’t do parsing, so the parsing thing you use probably does not parse as what this project expects. And, did you...

the micromark utils do a low an acorn instance to be passed, so that might also indeed allow the loose version? Worth to check, but might not be strong enough

Hi Marley! Thanks for contributing! And thanks for the sources! The problem with many things here is that they are very context and culture dependent. And, author dependent: and author...

> How about that we fix it too? Thanks. Good idea! Can you work on it?

This package is `markdown-rs`, not `mdxjs-rs`; this package does not compile MDX to JavaScript. There are no reproductions in this issue. If there is an issue, there needs to be...

We can report. Or crash. Or increment the name of our variables (`_components1`). What about `props`? That works *because* of this.

> This makes me think you mistook this issue from one in the MDX repo Indeed. Because whether these variables should be accessed affects MDX as a whole? Something could...

> Also lower case components are added on an as-needed basis, so it’s shape would unreliable for direct use. (side note: the distinction isn’t about lower-case vs upper-case btw) Agree...