Outline updated November 2026

Foundation14 hours delivered over 2 daysLive, online

Request this course

Svelte for Angular Programmers

Class Duration

14 hours of live training delivered over 2 days.

Student Prerequisites

  • Professional Angular development experience
  • TypeScript and HTML experience
  • Experience with CSS is helpful, but not required

Target Audience

Angular teams adopting Svelte and SvelteKit for new work or moving existing Angular apps to Svelte. Teams continuing on can move to Svelte Pro Techniques.

Description

This course teaches Svelte and SvelteKit to developers who already know Angular. Modern Angular and Svelte share a lot: both compile templates, use signals, and run without Zone.js. Each Svelte concept appears next to its Angular equivalent, such as computed() beside $derived and services beside reactive classes. On the framework side, students map the Angular Router, resolvers, guards, and interceptors to SvelteKit routing, load functions, and hooks. The course closes with a plan for moving an Angular codebase to Svelte, including AI-assisted component translation.

Learning Outcomes

  • Compare Svelte's compiler and runes with Angular Signals and zoneless change detection.
  • Set up a SvelteKit project and map it to the Angular CLI workflow.
  • Translate Angular templates, control flow, and pipes to Svelte markup and logic blocks.
  • Map signal(), computed(), linkedSignal(), and effect() to runes.
  • Translate inputs, outputs, model(), and content projection to props and snippets.
  • Replace attribute directives with attachments.
  • Replace injectable services with reactive state classes and type-safe context.
  • Map the Angular Router, guards, interceptors, and forms to SvelteKit equivalents.
  • Plan an incremental move from Angular 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; Angular 22 for side-by-side comparisons.

Training Topics

Svelte vs. Angular: Orientation

  • What is Svelte? What problem does it solve?
  • Svelte compiler vs. Angular compiler
  • Signals in both frameworks
  • Life without Zone.js
  • What replaces modules and decorators
  • No dependency injection container
  • Team and codebase considerations

Development Environment

  • npx sv create compared to ng new
  • sv add compared to ng add
  • Single-file .svelte components
  • Svelte extensions for VS Code and JetBrains
  • svelte-check vs. strict template checking

Templates

  • Interpolation and expressions
  • Attribute, property, and event syntax
  • {#if} compared to @if
  • {#each} compared to @for
  • {:else if} chains in place of @switch
  • {#await} compared to the async pipe
  • Class and style bindings
  • Derived values in place of pipes
  • Scoped CSS vs. view encapsulation

Runes vs. Angular Signals

  • $state compared to signal()
  • $derived compared to computed()
  • Writable deriveds compared to linkedSignal()
  • $effect compared to effect()
  • Deep reactivity vs. immutable signal updates
  • untrack compared to untracked()

Components

  • Svelte components vs. standalone components
  • $props() compared to input()
  • Callback props compared to output()
  • $bindable() compared to model()
  • Snippets compared to ng-content
  • Snippets compared to ng-template
  • bind:this compared to viewChild()
  • Attachments compared to attribute directives

Services and State

  • Reactive classes compared to injectable services
  • .svelte.ts modules for shared state
  • createContext compared to hierarchical injectors
  • Per-request state on the server
  • Where RxJS still fits
  • RxJS interop with Svelte stores

Events and Forms

  • DOM event attributes vs. event bindings
  • bind:value compared to ngModel
  • Svelte forms compared to Signal Forms
  • Form actions compared to reactive forms
  • Progressive enhancement with use:enhance
  • Validation with fail() and Standard Schema
  • Forms that work without JavaScript

Lifecycle and Effects

  • $effect cleanup compared to DestroyRef
  • onMount compared to ngOnInit
  • Equivalents of afterNextRender()
  • tick() vs. waiting for change detection

Routing with SvelteKit

  • File-based routing vs. route configuration
  • Layouts compared to nested <router-outlet>
  • page.params compared to ActivatedRoute
  • Automatic code splitting vs. lazy routes
  • Code splitting compared to @defer
  • goto compared to Router.navigate()

Data Loading and Server Code

  • Load functions compared to resolvers
  • Load functions compared to httpResource()
  • handle hooks compared to guards
  • handleFetch compared to HTTP interceptors
  • API routes in +server.ts
  • Experimental remote functions
  • SSR and prerendering vs. Angular SSR

Errors and Redirects

  • +error.svelte pages vs. ErrorHandler
  • <svelte:boundary> for component errors
  • redirect() compared to guard redirects

Testing

  • Vitest in both frameworks
  • Component tests with Testing Library
  • End-to-end tests with Playwright

Moving an Angular Codebase to Svelte

  • New features first, or route by route
  • Side by side behind a reverse proxy
  • Coexistence with custom elements
  • Angular Elements and Svelte custom elements
  • Mapping component and form libraries
  • Data access and internationalization
  • AI-assisted component translation
  • The Svelte MCP server
  • Code review and team adoption

Private team training

Bring this course to your team

Tell us about your team and we will tailor this outline to your tools, stack, and schedule. Courses can also be combined into a longer program.

  1. Tell us what you needYour tools, stack, team size, and timeline.
  2. We send a proposalA course or program, an outline adjusted to your team, and possible dates.
  3. Your team trains liveOnline or on-site, with courseware for every student.

Prefer to talk? Call +1 434-509-6890 or email help@cloudcontraptions.com.

We reply within 1 business day.

Training partner?