Repository navigation
chore: build the extension lists with inject-markdown's Markdown builders - #1776
Merged
Merged
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
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 change for users: the generated extension lists stay byte-for-byte the same.
scripts/gen-extension-list.mtsnow builds its Markdown with the builders ininject-markdown/markdown(released in inject-markdown 6.3.0) instead of the local mdast builder.scripts/lib/mdastBuilder.mts, which nothing else imported.scripts/package.json: drops@types/mdastandmdast-util-to-markdown, which nothing else used. It has no dependencies left: the script resolvesinject-markdownfrom the root.package.json: raisesinject-markdownfrom^6.2.1to^6.3.0.The old code passed
{ bullet: '-' }totoMarkdown. The builders also write-: the old and new scripts produce identical files instatic/generated/.