Repository navigation
1.9.0
Pico Engine 1.9.0 — release notes
Theme: See what a pico just did, and serve XMLUI views from the engine.
1.8.1 was versioned in git and never published. Those fixes are in this release. npm was last at 1.8.0.
Highlights
- Logging tab — per-pico in-memory ring (
PICO_ENGINE_LOG_RING, default 200) of events, queries, rules, policy decisions, entity writes, sends, and directives. Two-pane inspector, live stream, and a Filters dialog. Wrangler, PDS, subscription, and the developer UI stay hidden until checked. Design:logging-tab.md. - Same-engine calls — a
ctx:queryon this engine nests under the caller. Trace ids are not carried throughevent:sendorschedule. - XMLUI views — a shared function tagged
@viewis a page./ui/{eci}/{rid}/serves it; the developer UI shows View when a ruleset has views. Guide:pico-views.md. - Owner console — function expressions (for example
.mapcallbacks). - Ruleset cache — recompile when cached JavaScript is missing
init. Schema lookup uses the normalized ruleset URL. - Developer UI — Logging refresh and tab-gated loads, Testing split and ruleset choice kept across tabs, child creation keeps the chosen box color.
Upgrade
- Requires pico-framework ^0.8.2 (unchanged).
- Requires krl-compiler ^1.6.1. Fired and not-fired log lines include the rule name. Rulesets compiled earlier still run; names show up after a recompile or flush.
- The Logging tab reads the in-memory ring, not
pico-engine.log. A restart clears it. New activity fills it again. - Flush
io.picolabs.pico-engine-uiafter upgrade sologs()returns the transaction list without the old developer-UI filter. - Node 20 or 22.
Known deferrals
- Replay does not fill in event attributes.
- A send records the child transaction id and does not nest the other pico's rows.