Book Image

Svelte 3 Up and Running

By : Alessandro Segala
Book Image

Svelte 3 Up and Running

By: Alessandro Segala

Overview of this book

Svelte is a modern JavaScript framework used to build static web apps that are fast and lean, as well as being fun for developers to use. This book is a concise and practical introduction for those who are new to the Svelte framework which will have you up to speed with building apps quickly, and teach you how to use Svelte 3 to build apps that offer a great app user experience (UX). The book starts with an introduction to Svelte 3, before showing you how to set up your first complete application with the framework. Filled with code samples, each chapter will show you how to write components using the Svelte template syntax and the application programming interfaces (APIs) of the Svelte framework. As you advance, you’ll go from scaffolding your project and tool setup all the way through to production with DevOps principles such as automated testing, continuous integration, and continuous delivery (CI/CD). Finally, you’ll deploy your application in the cloud with object storage services and a content delivery network (CDN) for best-in-class performance for your users. By the end of this book, you’ll have learned how to build and deploy apps using Svelte 3 to solve real-world problems and deliver impressive results.
Table of Contents (9 chapters)

Routing on the browser

Backend developers are very familiar with the concept of routing in server-side applications: it allows the application (running on a web server) to render pages and content based on the URL the users requested.

For example, if our proof-of-concept application were a more traditional server-side one, we'd have to define at least the following routes:

  • GET / would return the list of all posts for a given day (with a date picker).
  • GET /add would render the form to add a new post.
  • POST /add would receive the data for the new post and store it in the database, then redirect the user to read the post.
  • GET /view/{id} would render the post with the given ID.

Because our app is a SPA, however, we are only shipping a single index.html file that contains all the different views. The state of the application controls what view is currently rendered.

Client-side routers are precisely the components that allow our SPA to render the correct...