Outline updated November 2026
Svelte for React Programmers
Class Duration
14 hours of live training delivered over 2 days.
Student Prerequisites
- Professional React development experience, including hooks
- JavaScript or TypeScript and HTML experience
- Experience with CSS is helpful, but not required
Target Audience
React teams adopting Svelte and SvelteKit for new work or moving existing React apps to Svelte. Teams continuing on can move to Svelte Pro Techniques.
Description
This course teaches Svelte and SvelteKit to developers who already know React. Each Svelte concept appears next to its React equivalent, so students reuse the mental models they have. The course maps JSX to templates, hooks to runes, render props to snippets, and Zustand stores to reactive classes. On the framework side, it maps React Router and Next.js routing, loaders, and Server Actions to SvelteKit. It ends with strategies for running React and Svelte side by side and translating components with AI coding agents.
Learning Outcomes
- Explain how Svelte's compiled, signal-based reactivity differs from React's re-rendering model.
- Set up a SvelteKit project and compare it to Vite React and Next.js.
- Translate JSX patterns to Svelte templates, logic blocks, and scoped styles.
- Replace hooks with runes, without dependency arrays or memoization hooks.
- Translate children, render props, refs, and context to Svelte equivalents.
- Replace Redux and Zustand stores with reactive state classes.
- Map React Router and Next.js data loading and Server Actions to SvelteKit.
- Map Suspense and error boundaries to
{#await}and<svelte:boundary>. - Plan an incremental move from React to Svelte.
Training Materials
All students receive comprehensive courseware covering all topics in the course. Courseware is distributed via GitHub in the form of documentation and extensive code samples. Students practice the topics covered through challenging hands-on lab exercises.
Software Requirements
Students will need a free, personal GitHub account to access the courseware. Students will need permission to install Node.js and Visual Studio Code on their computers. Also, students will need permission to install NPM Packages and Visual Studio Code extensions. If students are unable to configure a local environment, a cloud-based environment can be provided.
Software versions: Svelte 5 and SvelteKit 3 with Vite 8, TypeScript 6, and Node.js 22.17 or later; React 19 for side-by-side comparisons.
Training Topics
Svelte vs. React: Orientation
- What is Svelte? What problem does it solve?
- Compiler and signals vs. virtual DOM
- What carries over from React
- Team and codebase considerations
Development Environment
npx sv createvs. Vite andcreate-next-app- Adding tooling with
sv add .sveltefiles vs. JSX and TSX- Svelte extensions for VS Code and JetBrains
svelte-checkcompared totsc
Templates vs. JSX
- Markup and expressions vs. JSX
{#if}vs. conditional expressions{#each}vs.map()- Keyed each blocks vs. the
keyprop - The
classattribute vs.clsx - Scoped CSS vs. CSS modules
{@html}vs.dangerouslySetInnerHTML- Declaration tags vs. local variables
Runes vs. Hooks
$statevs.useStateanduseReducer- Mutation vs. immutable updates
$state.rawfor immutable data$derivedcompared touseMemo$effectcompared touseEffect- No dependency arrays or stale closures
- No
useCallbackand no rules of hooks - Reactive classes in place of custom hooks
Components
- Svelte components vs. function components
$props()with TypeScript types- Callback props, as in React
$bindable()vs. value and onChange pairs- Snippets vs.
childrenand render props bind:thisvs.useRef- Attachments vs. ref callbacks
createContextvs. React context
Events and Forms
- DOM event attributes vs. synthetic events
bind:valuevs. controlled inputs- Form actions vs.
useActionState - Progressive enhancement with
use:enhance - Validation with
fail()
Lifecycle and Effects
$effectcleanup vs.useEffectcleanuponMountvs. mount-only effects$effect.prevs.useLayoutEffect- No Strict Mode double invocation
State Management
- Reactive classes vs. Redux Toolkit slices
.svelte.tsmodules vs. Zustand stores- Context for per-request state
- Load functions vs. TanStack Query
- Reading legacy Svelte stores
Routing with SvelteKit
- File-based routing vs. React Router
- Layouts vs. App Router layouts
page.paramsvs.useParamsgotovs.useNavigate$app/statevs.useLocation
Data Loading and Server Code
- Load functions vs. loaders
- Load functions vs. Server Components
- Form actions vs. Server Actions
+server.tsvs. route handlers- Remote functions vs. server functions
- SSR, prerendering, and adapters
Errors and Async UI
+error.sveltevs. route error elements<svelte:boundary>vs. error boundaries{#await}vs. Suspense- Experimental
awaitin components - Redirects with
redirect()
Testing
- Vitest and Testing Library
- Testing runes and reactive classes
- End-to-end tests with Playwright
Moving a React Codebase to Svelte
- New routes first, or app by app
- Side by side behind a reverse proxy
- Mounting Svelte in React with
mount - Svelte custom elements in React
- Mapping UI kits and form libraries
- Data fetching and internationalization
- AI-assisted component translation
- The Svelte MCP server
- Code review and team adoption