What problem does it solve?
Upgrading a Nuxt project from @nuxtjs/mdc to Comark requires mapping changed APIs, AST formats, components, and plugin configuration, and doing this by hand is error-prone without a complete reference.
Core Features & Use Cases
- API Mapping: Provides side-by-side tables for parseMarkdown, createMarkdownParser, stringifyMarkdown/renderMarkdown, and result field changes (body/data to nodes/frontmatter).
- Nuxt Module Migration: Covers @comark/nuxt configuration, MDCRenderer/MDC/MDCSlot component replacements, defineMarkdownComponent, prose components, and Nuxt UI callout integration.
- Plugin & Pitfall Guidance: Maps remark/rehype plugins to Comark plugins (shiki, toc, emoji, summary) and lists common pitfalls like sync createMarkdownParser and opt-in emoji.
- Use Case: A developer upgrading a Nuxt content site asks the AI to convert their mdc.config.ts, MDCRenderer usage, and parser calls to Comark equivalents using this reference.
Quick Start
Migrate my Nuxt project from @nuxtjs/mdc to Comark, updating the parser calls, renderer components, and plugin configuration.