/explore
|
You are here 
|
chrisjayden.com | ||
| | | | |
www.matsimitsu.com
|
|
| | | | | Or, make sure your headers match, otherwise you'll get a lot of strange errors. | |
| | | | |
tiim.ch
|
|
| | | | | Learn why server-side rendering (SSR) using urql as a GraphQL client is not as straightforward as you might think and how to do it anyway. | |
| | | | |
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. | ||
