Skip to content

@solidjs/diagnostics@2.0.0-rc.7

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Sep 16:47
· 32 commits to main since this release
@solidjs/diagnostics@2.0.0-rc.7
b1c4399

Patch Changes

  • 6c8c956: Attribution: feedback() gains the fact tables that have no verdict of their own. flights counts, per async source, flights started, landed, and abandoned (superseded by a newer flight before landing — the re-ask-on-every-keystroke signature) with landed wall time. fallbacks measures, per loading boundary (named by owner path), how many times and for how long its fallback was shown and how many shows were sub-150ms flashes — the other end of the SILENT_HOLD spectrum. sources rows gain late/lateMs: acknowledged holds that still ran past holds.infoMs, where the affordance is not the whole answer. New AttributionHooks.boundaryFallback hook point at the boundary's source-set transitions. @solidjs/diagnostics exports the FlightStats and FallbackStats types; artifacts and the bridge carry the new tables through the existing feedback field.

  • d5aba4b: WIDE_WRITE and HOT_SCOPE_FANOUT diagnostics, and the reactivity-diagnostics and agent-loops skills, now prescribe a projection (createProjection, or a createStore(fn) keyed by id) as the fan-out repair. They previously named an API that is not part of 2.0 (#3304).

  • 1a1e2f2: Diagnostics: the responsiveness gate — holds and feedback in the artifact, expectNoSilentHolds, and Loop 4.

    The artifact (format v2) now carries attribution.holds — every transition hold the scenario caused, with the held writes, the blockers, the wait measured from the interaction, and which affordances acknowledged it — and attribution.feedback, the ranked sources/interactions tables folded from them. JSONL egress emits hold and feedback records; the browser bridge and the /__solid/diagnostics protocol gain holds() and feedback() live queries.

    New gates: expectNoSilentHolds(artifact, { maxSilentMs }) fails on any hold the screen never acknowledged (no isPending()/latest() reader, no optimistic value, no affects() mark, nothing painted) with the interaction, held write, blocker, and duration as evidence; expectHoldBudget(artifact, ms, { source }) bounds hold latency regardless of acknowledgment. ScenarioBudget gains maxSilentHoldMs and maxHoldMs; Vitest gains toHaveNoSilentHolds() and toStayWithinHoldBudget(ms). The agent-loops skill gains "Loop 4 — Responsiveness": read feedback.sources first, repair by shape (isPending → latest → createOptimistic), and the explicit anti-repair — never make the gate pass by moving the write off the async path. Types HoldEvent, ChangeOrigin, AttributionFeedback, FeedbackSource, FeedbackInteraction are exported.

  • f4d3c87: Responsiveness thresholds and the LONG_HOLD diagnostic.

    • SILENT_HOLD defaults tighten to holds: { infoMs: 100, warnMs: 200 } (from 300/500): RAIL's "feels instant" ceiling and the INP "good" ceiling. The engine measures to the commit, not the paint, so every number is a floor on what the user saw; the console's thresholds now sit at the strict end of the band.
    • New LONG_HOLD (responsiveness kind): an acknowledged hold whose quiescent tail — from the last write to join it to the commit — reached longHolds.infoMs (default 500ms), warn from longHolds.warnMs (1000ms). Measured from the last join so a hold that keeps taking input is judged by each wait, not its lifetime. The repair is a fallback: a Loading boundary keyed with on (a revealed boundary without on keeps the old content — that is the hold), a fresh boundary, or making the data fast. A silent long hold stays one SILENT_HOLD with the same repair appended and data.long: true.
    • HoldEvent.tailMs added; holdMs now runs from the interaction dispatch or the first parked flush, whichever is earlier (a node rewritten mid-hold keeps only its latest record, so the flush clock keeps the first wait from being forgotten). ChangeRecord.at stamps root writes.
    • feedback().sources[].late/lateMs replaced by long/longMs: holds whose tail reached the long-hold threshold, acknowledged or not.
    • @solidjs/diagnostics artifact format version 3 (tailMs on holds, long/longMs on sources); hold evidence in assertion failures includes tailMs.
    • RerunEvent.phase value "transition" renamed to "held" ("plain" | "held" | "optimistic") — the dev surface uses one word for the state.

  • Updated dependencies [215de3b]

  • Updated dependencies [6c8c956]

  • Updated dependencies [1a1e2f2]

  • Updated dependencies [7c14e23]

  • Updated dependencies [ef2b02c]

  • Updated dependencies [c6c415b]

  • Updated dependencies [6c8c956]

  • Updated dependencies [d5aba4b]

  • Updated dependencies [3ae0ca0]

  • Updated dependencies [ae46c92]

  • Updated dependencies [6c8c956]

  • Updated dependencies [1a1e2f2]

  • Updated dependencies [f98bd77]

  • Updated dependencies [fc7e626]

  • Updated dependencies [d50e855]

  • Updated dependencies [8f9f369]

  • Updated dependencies [c531e2a]

  • Updated dependencies [aed21ac]

  • Updated dependencies [b3c94be]

  • Updated dependencies [0653673]

  • Updated dependencies [6c8c956]

  • Updated dependencies [94fe5b4]

  • Updated dependencies [23477ae]

  • Updated dependencies [f4d3c87]

  • Updated dependencies [067e3bc]

  • Updated dependencies [8a65e5e]

  • Updated dependencies [f24e53d]

  • Updated dependencies [fa568d3]

  • Updated dependencies [d601119]

  • Updated dependencies [ac5159a]

  • Updated dependencies [de1c8b5]

  • Updated dependencies [c07a044]

  • Updated dependencies [01e3a57]

  • Updated dependencies [e346e61]

  • Updated dependencies [713a910]

  • Updated dependencies [e346e61]

  • Updated dependencies [0255729]

  • Updated dependencies [6c8c956]

    • @solidjs/signals@2.0.0-rc.7
Assets 2
Loading