MdFlow

Appearance

Appendix A — Reference Implementations ​

This appendix lists implementations of the MdFlow Standard that claim conformance. Listing here does not imply endorsement; implementations are self-reported.

A.1 @mdflow/core (TypeScript) ​

  • Language: TypeScript (ES2022+), distributed as ESM.
  • License: MIT.
  • Classes claimed: Class B + Class S.
  • Targets: Full stack, Extension host.
  • Plugins bundled: markdown-base, markdown-heading, markdown-code, markdown-quote, markdown-list, markdown-table, markdown-inline, markdown-link, highlight, custom-elements, interactive, events, code-actions, cursor, external-renderer.
  • Vectors: runs the full @mdflow/spec-tests suite.
  • Repository: https://github.com/<org>/mdflow

A.2 Framework wrappers ​

The following wrappers delegate parsing and rendering to @mdflow/core and therefore inherit conformance from it. They do not independently claim conformance:

  • @mdflow/react — React 18+ component.
  • @mdflow/vue — Vue 3 component.
  • @mdflow/svelte — Svelte 5 component.
  • @mdflow/angular — Angular standalone component.
  • @mdflow/lit — Lit-based custom element.
  • @mdflow/astro — Astro SSR integration.

A.3 Third-party implementations ​

(none at time of v1.0 draft)

Implementers wishing to list here SHOULD:

  1. Publish their vector run results alongside their release.
  2. File an issue against the MdFlow specification repository with a link to the release and the results.
  3. Maintain the listing with each minor release.

A.4 Implementation notes (informative) ​

The reference implementation's object pool, rAF scheduling, and sub-token patching optimizations are not normative. A conforming implementation MAY choose entirely different internal data structures and render strategies, provided the observable output matches the conformance suite.