solidjs / solid / 35947693006

74%

main: 89%

push

github

feat(web): server spans in the Performance panel over Server-Timing (#3617)

Performance tracks Stage 5. Dev and observe servers write the request's
timed work as Server-Timing metrics beside the trace entries:
`solid-invocation` on a server-function response, `solid-shell` and one
`solid-boundary` per boundary that waited and settled before the shell on
a document. Dev always; observe only while something on the server is
subscribed to the invocation/boundary records (no wire change without an
observer); prod carries no code. `desc` is sanitized to printable ASCII —
a non-ASCII header value throws from Headers.append, which hung a response
whose first write carried it.

`@solidjs/web/performance-tracks` reads the metrics back: `<id> · server`
spans beneath each call, placed against the resource's responseStart
(PerformanceObserver for late entries, centred in the call after 30 s),
and the document's navigation serverTiming painted at enable.

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

594 of 882 branches covered (67.35%)

Branch coverage included in aggregate %.

870 of 1133 relevant lines covered (76.79%)

24.67 hits per line