Test your Sapper knowledge with a free interactive quiz — 21 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What replaced Sapper, and roughly when did the Svelte team recommend the transition?
In this round
What replaced Sapper, and roughly when did the Svelte team recommend the transition?
What server-side rendering (SSR) capability did Sapper provide?
What kind of applications was Sapper (and universal SSR+hydration frameworks generally) particularly well suited for, motivating its creation in the first place?
What client-side navigation behavior did Sapper provide once an app was hydrated, as opposed to every link triggering a full page reload?
What was Sapper's relationship to Svelte itself?
Why would a developer maintaining an existing, older Svelte application today still need to understand Sapper, despite it being deprecated?
What build tool did Sapper's original tooling center around, as distinct from SvelteKit's Vite-based approach?
What general lesson does the Sapper-to-SvelteKit transition illustrate about relying on a young/evolving framework's "official" application layer?
What is Sapper?
What is a "server route" (an endpoint file, e.g. `src/routes/api/users.js`) in Sapper used for?
What was the purpose of Sapper's `preload()` function on a page component?
What does "code-splitting" (a capability Sapper provided) mean for an application's loaded JavaScript?