Explore >> Select a destination
|
You are here 
|
joyofcode.xyz | ||
| | | | |
khromov.se
|
|
| | | | | In this blog post we'll go over a lesser documented but powerful part of SvelteKit - event.locals. Locals are a way to register trusted, server-side, per-request state. The most common use case for locals is to associate some type of data with the current request. Example use cases for locals are: Since locals are per-request, they don't leak between requests, and disappear immediately when the request has been delivered to the user. Locals are common in other frameworks - you might already be familiar w... | |
| | | | |
hartenfeller.dev
|
|
| | | | | In this post, we look into how we can build our own Authentication and Authorization solution for SvelteKit. We will store and hash user credentials, create sessions with Cookies, and make the session info available to the app through hooks and locals. | |
| | | | |
haseebmajid.dev
|
|
| | | | | Out of date This article maybe a bit out of date as PocketBase is adding new features and deprecating old functions. If you encounter an issue with the setup see this issue by Dominick Hi everyone, I've been building a new bookmarking app, using SvelteKit and PocketBase. PocketBase, is an open-source backend, that we need to self-host 1. It is written in Golang, think of it similar to Firebase or Supabase. PocketBase will handle authentication for us, creating new users, and storing the password securely. You know things all apps need, that we don't want to spend a lot of times building ourselces. To learn more about authentication with SvelteKit I recommend checking out the web there are some fantastic tutorials available 2. | |
| | | | |
whitep4nth3r.com
|
|
| | | Learn how to build The Ultimate Theme Toggle for your website using JavaScript, CSS custom properties, local storage and system settings. No framework required! | ||
