CodeVetter · Repo Unpack · Behavior traces
solidjs/solid
Source inspection followed browser hydration and navigation, structured-state updates, asynchronous resource completion, and static HTML persistence. These traces name the local functions and identify external renderer boundaries explicitly. They describe implementation paths rather than runtime results observed during this investigation.
- Browser startup: the shared index calls hydrate(() => <App />, document); the web wrapper calls enableHydration before hydrateCore, whose implementation is imported through dom-expressions.
- Application initialization: App is wrapped by RouteHOC; the wrapper initializes a location signal from props.url or window.location.pathname, obtains useTransition, and provides location/pending/navigation helpers through RouterContext.
- Tab action: Link.navigate prevents default navigation, calls history.pushState, and invokes the context setLocation helper; that helper starts a transition, and App's matches predicates determine the Switch/Match branch.
- Profile loading: the wrapper creates a user resource with a 400 ms promise, creates an info resource sourced from user with initialValue [], and passes both accessors' values into a lazy Profile component containing a nested Suspense list.
- Signal update: createSignal's setter evaluates an updater and calls writeSignal; writeSignal queues invalidated computations within runUpdates, which calls completeUpdates and then runQueue/runTop/updateComputation.
- Structured-state update: createStore calls unwrap then wrap and returns setStore; setStore calls batch, selects updateArray or updatePath, and reaches setProperty, which emits signal-node notifications.
- Async completion: createResource.load calls fetcher and attaches promise handlers; loadEnd checks promise identity, completeLoad commits resource state, and Suspense.decrement clears its fallback when the pending counter reaches zero.
- SSR request: Express's catch-all handler passes req.url into App inside renderToStringAsync, awaits the result, and sends it; the rendering API crosses the web server re-export boundary into dom-expressions.
- HTML persistence: ssg/export.js maps index/profile/settings into entry/output/url records; renderStatic calls run for each, run spawns writeToDisk.js, and write calls the SSG entry before mkdir and writeFile.
- Custom-element lifecycle: customElement registers withSolid(ComponentType); withSolid creates a root and signal-backed props, inserts the component, updates props on property callbacks, and clears content/disposes on release.
- Server lazy rejection: load records a cast error and clears its cached rejected promise; the wrapper registers completion/error work with context.block, notifySuspense reaches completed, and Suspense routes errors toward an ErrorBoundary fallback.