Master the vocabulary behind Qwik City's file-based routing and resumability model.
0 / 5 completed
1 / 5
At standup, a dev wants file-based routing and layouts for a Qwik app. Which meta-framework provides this?
Qwik City is the meta-framework layer on top of Qwik core, adding file-based routing, layouts, and server-side data loading conventions. Qwik core alone handles fine-grained resumability but not routing. This split mirrors how Vite underlies many frameworks without providing routing itself.
2 / 5
During a design review, the team loads data on the server before the route renders. Which Qwik City API fits?
routeLoader$ defines a server-side function that fetches data before rendering and makes it available reactively to the route's components. It integrates with Qwik's resumability model so no redundant client fetch is needed. This is the idiomatic Qwik City data-loading primitive.
3 / 5
In a code review, a dev writes a function that handles a form POST on the server. Which Qwik City primitive fits?
routeAction$ defines a server-side action, typically triggered by a form submission, that can validate input and return a result consumed reactively by the page. It complements routeLoader$ for the write side of data flow. This pairing covers most server interaction needs in Qwik City.
4 / 5
An incident report shows a component's client-side JavaScript ran immediately even for content far below the fold. Which Qwik principle is being violated?
Qwik's core principle is resumability: no component JavaScript should execute until the user actually interacts with it, avoiding the eager hydration of traditional frameworks. Code running immediately for off-screen content suggests something bypassed lazy loading (e.g., an eager useVisibleTask$). Diagnosing and deferring that logic restores Qwik's lazy-loading benefit.
5 / 5
During a PR review, a teammate wants a nested route segment to share a common shell. Which Qwik City file convention provides this?
A layout.tsx file in Qwik City wraps nested routes within a directory with shared UI, similar to layout conventions in other file-based routers. Nested layouts compose automatically based on folder structure. This keeps shared chrome like navigation out of individual route files.