sscoble/pi-mono
1
0
Fork 0
mirror of https://github.com/badlogic/pi-mono.git synced 2026-11-05 23:37:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
pi-mono/packages/chord/src/web
History
Mario Zechner ff33ef42c4 feat(chord): telemetry from pages and workers stored by the server, who a span was for 
The four telemetry gaps (rows on commits, chord.host, microsecond times, a read-only store) and: pages record and
send span batches over their link to the server's ingest object (checked, capped, rate-limited, stamped browser and
with the link's principal); workers send theirs too, so the server is the store's only writer; principalAttributes
lets an app choose what a span records about its principal. The tutorial shows a real page's click traced to the
worker, with the trace viewer.
2026-11-04 11:59:14 +00:00
..
environment.ts feat(chord): Chord v2 is the package's root 2026-11-02 22:36:55 +00:00
index.ts feat(chord): messages and languages in the app kit (i18n) 2026-11-03 20:25:53 +00:00
language.ts feat(chord): messages and languages in the app kit (i18n) 2026-11-03 20:25:53 +00:00
page.ts feat(chord): telemetry from pages and workers stored by the server, who a span was for 2026-11-04 11:59:14 +00:00
README.md feat(chord): telemetry from pages and workers stored by the server, who a span was for 2026-11-04 11:59:14 +00:00
scripts.ts feat(chord): Chord v2 is the package's root 2026-11-02 22:36:55 +00:00
themes.ts feat(chord): Chord v2 is the package's root 2026-11-02 22:36:55 +00:00

README.md

web (browser side)

startPage (slice 11 §2) for the app's web entry, the base bundle the server builds: @earendil-works/chord/web. The server side is @earendil-works/chord/surfaces (webSurface).

startPage<P>({
	connect: () => new WebSocket(`${location.origin.replace(/^http/, "ws")}/chord`),
	modules: { "@acme/app/v3": api, "@acme/app/v3/web": apiWeb, react: React, "react/jsx-runtime": jsx },
	core: [{ name: "@acme/web", facet: webCore }],
	canRetry: async () => true,                    // false: stop reconnecting (a guest's ended share)
	onConnection: (state) => setBanner(state),     // connecting | connected | waiting
	render: (host) => createRoot(root).render(<HostProvider host={host}><App /></HostProvider>),
	telemetry: true,                               // record: spans sent to the server's PageTelemetry
});
  • The page's inline bootstrap (PageAssets.bootstrap, the response's nonce) defines chordFacet before the combined file runs; its scripts queue, and startPage takes them (scripts.ts). Later scripts load with <script src>, one each, and resolve the fetch that asked for them; no eval (the page's CSP: 'self' and the nonce).
  • The kit's Themes provider is among the core facets; the active theme (the registry, the user's ThemeChoice, prefers-color-scheme) is written as CSS custom properties and color-scheme on :root (themes.ts), no reload.
  • The kit's Translations provider is among them too; the active language (the registry, the user's LocaleChoice, navigator.languages, followed on languagechange) is the host's language for useMessages, and lang and dir on the root element (language.ts, followLanguage); reports reach onError as { kind: "messages", report }.
  • A new set's plugin stylesheets replace the old ones (syncStylesheets); an outdated page reloads.
  • With telemetry: true the page's host records in memory (TelemetryRecorder, span ids browser:<incarnation>:<n>) and sends finished spans to the server's PageTelemetry every 3 s and when the page is hidden; a click is a trace of its own with host.root(fn, ctx, { trace: { name } }). The kit's server serves the object when it has a store.
  • Wakes (environment.ts): visible again, online, pageshow from the back/forward cache, Chromium's network change.

Tests in a real browser: test/node/web/ (Chromium: CHROMIUM_BIN, else chromium-docker; skipped without).