explaingit

sveltejs/sapper

★ 6,938TypeScriptAudience · developerComplexity · 1/5LicenseSetup · hard

TLDR

Sapper was a framework for building full web applications with Svelte, handling routing and server-side rendering. It is now deprecated, SvelteKit is its official replacement and what you should use instead.

Mindmap

mindmap
  root((Sapper))
    Status
      Officially deprecated
      Archived for reference
      Replaced by SvelteKit
    What it did
      Page routing
      Server-side rendering
      Static site generation
    Migration
      Use SvelteKit instead
      Reference for legacy apps
    Tech
      TypeScript
      Svelte
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Read the archived repository to understand historical Sapper patterns if you are maintaining a legacy Sapper project.

USE CASE 2

Migrate an existing Sapper app to SvelteKit by using this repo as a reference for the original routing and structure conventions.

Tech stack

TypeScriptSvelteJavaScript

Getting it running

Difficulty · hard Time to first run · 1day+

Deprecated, do not use for new projects, migrate to SvelteKit instead.

Open source under the MIT license, use freely for any purpose, including commercial, with no restrictions beyond keeping the copyright notice.

In plain English

Sapper was a framework for building web applications using Svelte, a JavaScript tool for creating user interfaces. It handled the parts of a web project that go beyond a single page, like routing between pages, server-side rendering, and generating static sites. The project has been officially deprecated and is no longer actively developed. The README directs users to SvelteKit, Sapper's successor and the now-recommended way to build Svelte applications. SvelteKit covers the same ground as Sapper with a more complete and maintained foundation. The repository is archived and kept available for historical reference and for projects that were built on Sapper before the transition. No new features are being added. The README is brief, containing only the deprecation notice, a link to the successor project, and a note about financial support for the Svelte ecosystem via OpenCollective.

Copy-paste prompts

Prompt 1
I have an old Sapper project and need to migrate it to SvelteKit. List the main structural differences between Sapper and SvelteKit and what I need to change.
Prompt 2
Explain how Sapper's file-based routing worked compared to SvelteKit's current routing system, so I can update my existing routes.
Prompt 3
My Sapper app uses server-side rendering. Walk me through the equivalent SvelteKit setup so I can migrate without breaking anything.
Open on GitHub → Explain another repo

← sveltejs on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.