Repository navigation
chore: remove obsolete markdown-it 14 typings after v15 migration - #82
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.
Why
PR #75 successfully upgraded the framework-free site to markdown-it 15.0.3, which ships first-party TypeScript declarations. The repository was still installing the obsolete @types/markdown-it 14.1.2 package, risking two competing parser type definitions and unnecessary tooling weight.
Changes
package.json(the repository intentionally has no checked-in lockfile).@types/markdown-itwhen markdown-it 15+ is pinned.SCARP-DOCS-ENGINE.md.Verification
Require all eight CI jobs, especially TypeScript 6 strict typechecking, Markdown renderer tests, bilingual route parity, offline browser/a11y and pinned Scarp compiler conformance. No new frontend framework and no stable release.