v9: rewrite for spec compliance and speed #725
Conversation
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
🦋 Changeset detectedLatest commit: c6b45e0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
quantizor
changed the title
quantizor
force-pushed
the
maintain
branch
2 times, most recently
from
f137764 to
10f758a
Compare
markdown-to-jsx is now 100% gfm & commonmark compliant, while being more than 10x faster depending on the benchmark at all input sizes it is the fastest markdown parser... maybe ever? definitely the fastest javascript-based markdown parser to achieve this there were some tradeoffs, notably the bundle size if we dropped html entity compliance down to the absolute bare minimum, the library would be much smaller and still much larger than earlier majors however, I think in 2025 the performance is more worthwhile and enables fun scenarios like butter-smooth live authoring plus now you can use the parser directly and build your own renderer if you want
quantizor
force-pushed
the
maintain
branch
2 times, most recently
from
7d1c79b to
4455491
Compare
Owner
Author
|
|
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.
no real public API changes but...
yeah
Note
Major v9 rewrite introducing new core structure, build system, demo site, tooling, and package exports while removing legacy code/tests.
index.tsx, large spec files) and adopt new v9 structure (consuming fromsrc/react,src/html,src/markdown).bunup.config.tsand plugin to strip debug code; updatebunfig.toml.package.json: Node >=18, modern deps, new exports (./react,./html,./markdown), scripts for build/dev/bench/metrics.docs/index.html; implement new demo app insite.tsxwith syntax highlighting, presets, and visuals.Written by Cursor Bugbot for commit c6b45e0. This will update automatically on new commits. Configure here.