CodeVetter · Repo Unpack · Feature catalog
QwikDev/qwik
The primary user is an application developer using components, reactive state, routing, server functions, and deployment adapters. The inspected public surfaces also provide scaffolding, React interoperability, lint rules, and local inspection tools. Insights adds telemetry ingestion and an authenticated dashboard foundation. This catalog covers evidenced feature families; the capped inventory and selective source reads do not establish an exhaustive list of every example, documentation screen, or integration.
- Core exports component$, QRL boundaries $, sync$, event$, JSX helpers, Slot, and client rendering APIs.
- Developer state APIs include useStore, useSignal, computed signals, async signals, contexts, scoped styles, tasks, visible tasks, resources, and serializers.
- Each, Show, Pending, and Catch are exposed control-flow/error primitives; optimizer experimental flags include each, show, pendingBoundary, catchBoundary, and blockSSR.
- Event handling supports element, document, and window scopes, passive variants, preventdefault attributes, stoppropagation attributes, and late registrations.
- routeLoader$ supplies ComputedSignal data, per-loader endpoints, search-parameter allowlists, ETags, cache-control options, and strict-loader defaults.
- Route actions provide browser submission state and form completion events; JSON action handling runs validators and can return explicit loader invalidation hashes.
- server-function requests can return either a serialized value or an async-iterator stream using application/qwik-json and text/qwik-json-stream.
- Router exposes adapters for Azure SWA, Cloudflare Pages, Cloud Run, Bun, Deno, Node, Netlify Edge, static generation, and Vercel Edge.
- create-qwik supports argument-based or interactive startup; the argument path accepts template, output directory, --force, and --installDeps.
- React interoperability exports qwikify$ and reactify$; qwikifyQrl tracks props, resolves the React component lazily, maintains a React root, and schedules root cleanup.
- Developer tooling includes recommended/strict ESLint rule sets and MCP tools for project information, route lists, browser errors, page inspection, and offline documentation.
- Insights accepts symbol timing telemetry, mounts an Insights component and RouterOutlet, and integrates GitHub sign-in, sign-out, and session APIs.