Changelog
Release notes for aparté 1.10.1: what changed in each @aparte package, and what to update.
On this page
Version 1.10.1
Every @aparte/* package ships at this version (they are released in lockstep).
Patch Changes
-
08b0986:
AparteConversationSelectDetail.idis nowstring | null:nullmeans a new conversation. Handle it where you read the event’sidas astring.aparte-conversation-selectwith{ id: null }is the documented way for a New chat button to start a new conversation, and every chat bound to a manager honours it, but the type saidid: string: dispatching it took a cast, and a typed listener’s “new conversation” branch read as dead code. The list itself still sends a row’s id. A listener that passesidon tosetConversationId()or aconversationIdprop needs nothing, since both takestring | null; one that uses it as astring(an index, a lookup key) now gets a type error wherenullwas always possible at runtime.@aparte/core -
3e390fc:
onApprovalModeChange(and any listener typed fromapprovalModeElement) now receivesApprovalModeChangeDetail, whosemodeandpreviousModeareApprovalMode; drop the guard or cast you used to index aRecord<ApprovalMode, …>.The switch and the
/approvalcommand only ever send one of the four modes, but the element’s spec typed the detail as core’sAparteApprovalModeChangeEventDetail, where both arestring, socreateAparteElement(approvalModeElement)called back with astring.ApprovalModeChangeDetailis new, exported from the plugin, and extends core’s type, so a listener on the DOM event map keeps compiling. Core’s type staysstring, for a host that registers modes of its own.@aparte/plugin-approval -
b4bdc29:
<AparteChat conversationId={id}>now draws that conversation when it mounts, also when the conversation manager already holds it loaded; asetConversationId(id)after mount is no longer needed.Nothing to change in your code; remove the workaround if you added one. A conversation the manager holds (one another chat had open, on the same manager) is drawn at once, during the chat’s mount. The
messagesprop’s effect then ran for the first time, took the initial[]for a list pushed by the parent, and replaced the transcript with it: the chat showed its empty state whilegetConversationId()returned the id. The effect’s first run is now recognised as the value the chat was created with. A conversation that has to be fetched (loadFull) was not affected, nor were Vue, Svelte or Angular, whosemessageswatchers do not run on mount; each wrapper now has a test for this case.@aparte/react
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-artifacts, @aparte/plugin-ask-user, @aparte/plugin-cards, @aparte/plugin-chartjs, @aparte/plugin-compaction, @aparte/plugin-diff, @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-subagents, @aparte/plugin-titler, @aparte/plugin-triggers, @aparte/angular, @aparte/svelte, @aparte/vue, @aparte/locales, @aparte/docs-mcp.