Quick start
@fluxdown/core turns changing Markdown into content blocks you can subscribe to. It is framework independent and works without a browser. You decide whether each block becomes a component, data, or another kind of output.
Use it to build a framework integration, a custom renderer, or a reactive Markdown pipeline.
Install
This example also installs the packages that provide the public content block and HAST types.
Get content blocks
Start with a minimal renderer that returns each content block unchanged. This lets you inspect its HTML syntax tree, or HAST.
There are three parts to this example:
textholds the full Markdown received so far. Callingnextupdates the output.BlocksRendererdecides the output format. Here it preserves content blocks; an app could return components for its target framework.coreconnects input and output.core.value.valueis the current output list, andblock.value.valueis a block's current HAST.
S and render create this reactive data flow. D passes the renderer class as a plain value. All three come from stative.
What is included
Core includes presets for Markdown syntax, HTML processing, syntax repair, and streaming transformations. build controls compilation features. Smooth output and the trailing fade are off by default and can be enabled separately.
Core does not provide a default UI. In the example, renders: [] means that this renderer works directly with blocks and does not need node-level render plugins.
Next steps
Read State and updates to connect changing text and subscribe to content blocks in your own interface.