The runtime

Effect-typed: what this page covers uses Effect's own types, so it moves to a new Effect major only in a Wardic major (the roadmap).

A WardicProvider builds one Effect runtime for everything under it, over its Environment: the clock, the frame loop, the renderer, the probe and the rest. These run Effect code of your own on it, for building on Wardic, or reading what it reads.

import { runScoped, useWardicRuntime } from "@wardic/solid" // or "@wardic/solid/unstable/v2"

const runtime = useWardicRuntime()
runScoped(runtime, Stream.runForEach(ticks, (tick) => Effect.sync(() => setTick(tick))))

• useWardicRuntime() is the nearest provider's runtime. It throws outside a provider. A server render doesn't build it: hold it, but run on it only once the element has mounted (Solid 1's onMount, Solid 2's onSettled).
• runScoped(runtime, effect) runs effect and interrupts it as the current owner is cleaned up, its Scope closed with it, and returns its fiber. A failure is logged as wardic.runScoped: a fiber failed and reported to the Environment's error reporters; an interruption is neither. On a server it starts nothing, and while hydrating it starts once the page has mounted.
• useWardicFiber(() => effect) is runScoped on the provider's runtime, the thunk called once.

The services

Code run on the runtime can use the Environment's services, each an Effect service:

@wardic/dom's DomLive provides them in a browser, and @wardic/test's TestLive in a test. See Observability for the logs and traces they give.

Types

• WardicRuntime: the runtime, a ManagedRuntime of its services.
• WardicServices: the services, as a union.