@solidjs/web

@solidjs/web is the renderer. It turns the component tree that solid-js describes into DOM in the browser and into HTML on the server, and it hosts the server-side runtime for server functions and request handling.

The package has a browser build and a server build. Bundlers pick the right one from the export map, so the same import works in both places:

import { render, hydrate, isServer } from "@solidjs/web";

Rendering and SSR

Rendering and SSR explains the three rendering paths and hydration.

• render mounts a tree into a DOM element and returns a dispose function.
• hydrate attaches a tree to server-rendered HTML.
• getHydrationWriter and takeHydrationValue give a data library its own keyed channel from the server render to the hydrating client.
• renderToString renders synchronously to a string; renderToStream streams the shell and then each boundary as it settles.
• httpStatus and httpHeader declare response metadata from inside the tree.
• clientOnly defers a component to the browser.
• isServer and isDev are build-time constants.

Head

• useHead registers tags with the ambient head registry; HeadTag describes them.
• @solidjs/meta wraps the registry in components; Head and metadata shows both.

Components

• Portal renders children elsewhere in the document.
• dynamic creates a component from a reactive source.

JSX properties

Attributes with renderer-specific behavior: ref, class, style, textContent, and innerHTML.

Server functions

The runtime behind "use server": declarations such as GET and live, per-call invoke options, and the host integration hooks. The Server functions index groups them; the Server functions guide covers application patterns.

Request and response

Working with the request on the server: getRequestEvent, the response helpers respond, redirect, and reload, cookies, safe errors, and getTraceContext for the request's W3C trace. The Request and response index lists them all.

Performance tracks

enablePerformanceTracks from @solidjs/web/performance-tracks paints the attribution engine's records and the runtime's server-function calls as tracks in the Chrome Performance panel; Performance shows how to read them.