Skip to content

perf: Optimize parser safety and rendering consistency - #1

Merged
Fuyeors merged 3 commits into
mainfrom
fix/parser-performance-security
Aug 18, 2026
Merged

perf: Optimize parser safety and rendering consistency#1
Fuyeors merged 3 commits into
mainfrom
fix/parser-performance-security

Conversation

@Fuyeors

@Fuyeors Fuyeors commented Aug 18, 2026

Copy link
Copy Markdown
Member

Summary

  • Bound recursive block and inline parsing depth and make parser IDs deterministic within each document.
  • Cache inline token positions and fenced block extraction to avoid repeated scans on hostile or repeated inputs.
  • Validate link protocols and color values at parser and renderer boundaries, with consistent core, Lit, and Vue output.
  • Add FFM regression coverage, strict library/test typecheck configs, reproducible ESM build output, and CI quality gates.

Validation

  • pnpm install --frozen-lockfile --ignore-scripts
  • pnpm --filter @fuyeor/markdown-parser typecheck
  • pnpm --filter @fuyeor/markdown-parser test:unit
  • pnpm --filter @fuyeor/markdown-parser test:ffm
  • pnpm --filter @fuyeor/markdown-parser build
  • Strict standalone typechecks for Lit and Vue renderers
  • pnpm --filter @fuyeor/markdown-parser-playground build
  • git diff --check

The existing full CommonMark/GitHub compatibility corpus remains a separate compatibility suite because it contains pre-existing specification mismatches outside this focused change.

@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
markdown-parser-playground Error Error Aug 18, 2026 11:48pm

@Fuyeors
Fuyeors merged commit e9a7fa9 into main Aug 18, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant