Repository navigation
feat: add a markdown-exit/core entry without linkify-it - #41
Merged
Merged
Conversation
serkodev
force-pushed
the
feat/core-entry
branch
from
November 3, 2026 08:34
c9f567d to
bf012bf
Compare
This was referenced Nov 3, 2026
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.
resolves #39
because
Parserrunsnew LinkifyIt()for every instance, linkify-it is in every bundle, even for apps that never enablelinkify.this adds a
markdown-exit/coreentry that never imports linkify-it. the default entry registers it, somarkdown-exitbehaves exactly as before, andmd.linkifystays a plain eager field. inmarkdown-exit/core,md.linkifyis unset until you assign one, and enablinglinkifywithout it throws an error that says so. a test bundles both entries with vite and checks that only the default one imports linkify-it.markdown-exitmarkdown-exit/core