Repository navigation
feat: parse MDX syntax as distinct nodes - #145
Merged
Merged
Conversation
Add MDX parsing and source map entry points. Keep ESM, JSX attributes, and expressions separate from Markdown text. Add MDX node, source map, package, and type tests. No sensitive data was changed. Refs #144
Test the Chinese MDX sample with MDX 3.1.1. Check AST parity, source ranges, and unchanged ESM, JSX attributes, and expressions. Compile the repaired source with GFM and math plugins. Refs #144
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
parseMdxandparseMdxWithSourceMap.Verification
pnpm run buildpnpm run lintpnpm run test(2021 tests pass)The parser repository has no CLI
--fixentry point.The CLI rejection tests belong in the CLI repository.
No sensitive data was changed or shared.
Closes #144