CodeVetter · Repo Unpack · Data flow
solidjs/solid
Reactive reads create dependency edges, and setters propagate invalidation through computation and effect queues. Stores translate property access and path updates into the same signal machinery, while resources translate asynchronous results into state and Suspense notifications. Server rendering uses hydration context to associate resources and fragments, and static generation adds a subprocess and filesystem output boundary.
- createSignal allocates SignalState with value, observers, observerSlots, and comparator; its getter binds readSignal and its setter delegates to writeSignal.
- readSignal records bidirectional dependency slots between the active Listener and the signal, resolves stale memos, and chooses tentative values during a running transition.
- writeSignal applies equality filtering, marks observers stale, queues pure computations separately from effects, and marks downstream memo consumers pending.
- runComputation installs a computation as Owner and Listener during its callback and restores both afterward; cleanNode removes dependency edges, child scopes, and cleanup callbacks.
- Store proxy reads lazily allocate per-property signal nodes only when tracking requires them; nested wrappable values receive proxies, while ownKeys subscribes to the self node.
- setStore batches updatePath/updateArray against the unwrapped object; setProperty mutates or deletes a property and notifies property, existence, array-length, and self observers.
- A resource source is memoized when callable; load obtains its current key, invokes the consumer fetcher untracked, records its promise, and sets pending or refreshing state.
- Resource loadEnd accepts a completion only when its promise matches pr, then completeLoad updates value/state/error and decrements subscribed Suspense contexts.
- Server resources are keyed by sharedConfig context IDs; asynchronous load stores resolved data in ctx.resources, calls notifySuspense, and passes values or promises to ctx.serialize.
- Hydration consumes deterministic context IDs: createComponent advances into a child context, client resources look up serialized values, and web hydrate first enables hydration behavior.
- provideRequestEvent stores an AsyncLocalStorage instance on globalThis under RequestContext and runs the supplied callback with its request event; it rejects non-server use.
- Static generation passes entry/output/url into a Node child process; writeToDisk dynamically imports the entry, calls its default export with the URL, creates the output directory, and writes returned HTML.