Test your Sapper knowledge with a free interactive quiz — 21 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What was the purpose of Sapper's `export()` command / static export capability?
Questions in this quiz
What was the purpose of Sapper's `export()` command / static export capability?
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?
What server-side rendering (SSR) capability did Sapper provide?
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 one of the main technical/architectural motivations for building SvelteKit as a replacement rather than continuing to iterate on Sapper directly?
What does it mean that SvelteKit's migration guide from Sapper described changes to the routing file-naming convention (e.g. moving away from some of Sapper's specific special filenames)?
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 kind of applications was Sapper (and universal SSR+hydration frameworks generally) particularly well suited for, motivating its creation in the first place?
What routing convention did Sapper use to map files to application routes?