Qwik Patterns

Quick Guide: Qwik is resumable rather than hydrated — the server serializes application state into the HTML and the client picks it up without re-executing framework code. Every $ suffix marks a lazy-loading boundary the optimizer splits into its own chunk, so only the code for the interaction a user actually triggers is downloaded. component$ wraps every component, useSignal/useStore hold state, routeLoader$ supplies server data, routeAction$ handles mutations, and server$ is ad-hoc RPC. The constraint everything else follows from: anything captured across a $ boundary must be serializable.

Detailed Resources:

• examples/core.md — typed props, signals, stores, tasks, resources, events, scoped styles
• examples/routing.md — route files, nested layouts, loaders, actions, server$, endpoints, middleware, navigation
• examples/serialization.md — what crosses the $ boundary, noSerialize, lean closures, QRL props
• reference.md — project layout, import cheat sheet, serializable-type table