CodeVetter · Repo Unpack · System map
QwikDev/qwik
The repository distributes a framework through several packages rather than running as one application. Core exposes separate client, server, optimizer, and CLI surfaces, while Router connects generated route configuration to platform middleware. Supporting applications include documentation and Insights, and development tooling includes MCP inspection. Build and deployment commands below are source-defined capabilities, not commands executed during this investigation.
- The pinned branch describes Qwik v2 as resumable, with VNode runtime work, rewritten reactive primitives, and a new serialization mechanism.
- @qwik.dev/core publishes conditional development/production runtime exports, an internal surface, JSX runtime exports, and a qwik CLI executable.
- renderToString delegates to renderToStream; streaming creates an SSRContainer, installs the server platform, renders JSX, and flushes buffered output.
- Browser startup is owned by qwikloader.ts, which turns window._qwikEv into a registration object and installs scoped event listeners.
- Router has buildtime-generated virtual modules and shared runtime route matching; requestHandler is the request entry used by adapters.
- createQwikPlugin selects @qwik.dev/ts-optimizer or @qwik.dev/optimizer; QWIK_OPTIMIZER=ts|rust overrides the option and invalid values throw.
- The Rust workspace includes optimizer core and NAPI members, lists then excludes the WASM member, and configures a size-oriented release profile.
- Insights owns persistent application, symbol, error, and manifest tables through Drizzle's libSQL database type and an initialized module-level database handle.
- The workspace spans packages/* and e2e/*, requires strict engine compatibility, and pins pnpm 11.22.0 with Node >=22.18.0 at the root.
- Root build.core.dev, build.full, test.unit, and browser-specific test scripts define the contributor build/test surface; docs deployment consumes CI artifacts and publishes to Cloudflare Pages.