Knowledge Base

Renamed components

Comark's framework components were renamed to describe what they render. Old names and props still work as deprecated aliases.

Comark's framework components were renamed so that names describe what they render rather than the library they come from: you render Markdown, with Comark. The Comark brand is unchanged everywhere else — package names (comark, @comark/vue, ...), parser APIs (parse, renderMarkdown, autoCloseMarkdown, ...), and AST types (ComarkTree, ComarkNode, ...) all keep their names.

Component names

Old nameNew namePackage
ComarkMarkdown@comark/vue, @comark/react, @comark/svelte, @comark/nuxt (auto-import)
ComarkRendererMarkdownParsed@comark/vue, @comark/react, @comark/svelte, @comark/nuxt (auto-import)
ComarkClientMarkdownClient@comark/react
ComarkLiveMarkdownLive@comark/react
ComarkAsyncMarkdownAsync@comark/svelte/async
ComarkNode (component)MarkdownNode@comark/svelte, @comark/angular
ComarkComponentMarkdown@comark/angular
ComarkRendererComponentMarkdownParsed@comark/angular
defineComarkComponentdefineMarkdownComponent@comark/vue, @comark/react, @comark/angular, @comark/nuxt
defineComarkRendererComponentdefineMarkdownParsedComponent@comark/vue, @comark/react, @comark/angular, @comark/nuxt

The Angular selectors changed accordingly: <comark><comark-markdown>, <comark-renderer><comark-markdown-parsed>, and <comark-node><comark-markdown-node>.

Prop names

Old propNew propComponent
markdownvalueMarkdown (and variants)
treevalueMarkdownParsed

All other props are unchanged (components, plugins, options, streaming, caret, unwrap, data, comarkKey, ...).

Backward compatibility

The old component names and props still work as deprecated aliases. Using one logs a one-time warning in the browser console during development to help you migrate. The aliases will be removed in a future major version, so update your imports and templates when convenient.