All versions since 1.0.1

On this page

Overview
1.0.1
1.0.2

All versions

1.0.1

Every @aparte/* package ships at this version (they are released in lockstep).

Patch Changes

b9ecb6a: A streamed reply no longer shows raw Markdown, such as the ** of a bold, for a moment at the start of a text or reasoning block. Nothing to change in your code.

Who saw it: apps on @aparte/plugin-marked/streaming, or on marked beside @aparte/plugin-streaming-markdown (the pair Getting started sets up). With @aparte/plugin-streaming-markdown alone the first chunk was already formatted. It lasted until the next chunk arrived: a reply opening on **Sure** flickered its asterisks, and a block whose first chunk was Done: **Book showed it as typed.

Why: a new segment’s first chunk was drawn by the one-shot Markdown provider, which reads a half-written reply as finished text, and the streaming renderer (which closes what the model has not closed yet: remend for marked) only took over from the second chunk. The stream parser’s text carries no isStreaming flag, and a segment’s setup read that as finished, because a restored message’s segments carry none either. Now a text or reasoning segment flagged isStreaming: true is written by the streaming renderer from its first chunk; addSegment on a streaming bubble treats an unflagged one as arriving; and populateBubbleFromMessage flags the last segment of a message whose status is streaming. A segment set by hand with setSegments is still drawn as finished, and every segment drawn this way is settled when the message stops, as one written chunk by chunk always was. _@aparte/core

_{Version-only bumps (no changes of their own): @aparte/engine, @aparte/runner-ag-ui, @aparte/runner-n8n, @aparte/provider-ai-sdk, @aparte/provider-openai-compat, @aparte/provider-scenario, @aparte/provider-transformers, @aparte/plugin-approval, @aparte/plugin-artifacts, @aparte/plugin-ask-user, @aparte/plugin-cards, @aparte/plugin-chartjs, @aparte/plugin-compaction, @aparte/plugin-echarts, @aparte/plugin-katex, @aparte/plugin-marked, @aparte/plugin-mermaid, @aparte/plugin-model-selector, @aparte/plugin-shiki, @aparte/plugin-storage-idb, @aparte/plugin-streaming-markdown, @aparte/plugin-titler, @aparte/angular, @aparte/react, @aparte/svelte, @aparte/vue, @aparte/locales, @aparte/docs-mcp.}

1.0.2 Latest

Every @aparte/* package ships at this version (they are released in lockstep).

Patch Changes

d8a544c: Enter now sends what is written in a question’s text field or an approval’s instruction; Shift+Enter starts a new line in the instruction. Nothing to change in your code.

Who saw it: anyone answering a panel from the keyboard. In an approval’s “Or tell it what to do instead…”, Enter added a line and sent nothing; in a question’s text box or its “Other…” field, it did nothing. The composer’s button was the only way out.

Why: a panel takes the editor’s place, and the editor was the only thing listening for the key. The composer now listens on the panel too, and Enter there goes through submit(), so it follows the same gates as the button: nothing written, nothing sent; a panel put aside sends nothing.

submit-on-enter="false" swaps the keys here as it does in the editor. A multi-line answer (multiline: true) keeps Enter for its next line. A panel of your own passed to showPanel() gets the same behaviour on its one-line fields; a field that handles Enter itself and calls preventDefault(), such as a combobox, keeps the key. _@aparte/core