Announcing SvelteKit Auth: Bringing NextAuth.js to all frameworks

Link to headingWhy SvelteKit?

The Auth.js open-source team targeted providing a simple authentication solution for Next.js first with the creation of NextAuth.js. However, we also are big fans of the SvelteKit framework. With today’s SvelteKit 1.0 release, we figured now was the perfect time to share what we’ve been up to.

SvelteKit (for Svelte) is conceptually similar to Next.js for React. It provides an opinionated framework for building your Svelte applications. We felt this made it the perfect candidate for a simple, low-configuration authentication library that supports many of the most most popular OAuth platforms like Google, Facebook, GitHub, and more.

Link to headingUsing SvelteKit Auth with SvelteKit 1.0

After installing @auth/sveltekit and @auth/core, we first need to define which OAuth providers we want to configure our application to use. Let’s use GitHub, for example.

1
import SvelteKitAuth from "@auth/sveltekit"
2
import GitHub from '@auth/core/providers/github';
3
import { GITHUB_ID, GITHUB_SECRET } from "$env/static/private"
4

5
export const handle = SvelteKitAuth({
6
  providers: [
7
    GitHub({ clientId: GITHUB_ID, clientSecret: GITHUB_SECRET }),
8
  ]
9
});

We’re able to read our environment variables to securely configure the GitHub OAuth provider. Next, we can allow users to sign in.

SvelteKit Auth provides helpful methods to signIn and signOut on user actions. In the following example, we check if the user is authenticated for the main index route. If we have session data, we’re able to display the user’s avatar and name. Otherwise, we can show a sign-in button.

1
<script>
2
	import { signIn, signOut } from '@auth/sveltekit/client';
3
	import { page } from '$app/stores';
4
</script>
5

6
<p>
7
	{#if Object.keys($page.data.session || {}).length}
8
		{#if $page.data.session.user.image}
9
			<span style="background-image: url('{$page.data.session.user.image}')" class="avatar" />
10
		{/if}
11
		<span class="signedInText">
12
			<small>Signed in as</small><br />
13
			<strong>{$page.data.session.user.email || $page.data.session.user.name}</strong>
14
		</span>
15
		<button on:click={() => signOut()} class="button">Sign out</button>
16
	{:else}
17
		<span class="notSignedInText">You are not signed in</span>
18
		<button on:click={() => signIn('github')}>Sign In with GitHub</button>
19
	{/if}
20
</p>

We could also put this logic inside of a shared layout for a group of routes, if we prefer. Finally, we can also easily protect routes we don’t want to allow access to for unauthenticated users.

1
import { redirect } from "@sveltejs/kit"
2
import type { PageLoad } from "./$types"
3

4
export const load: PageLoad = async ({ parent }) => {
5
  const { session } = await parent()
6
  if (!session?.user) {
7
    throw redirect(302, "/")
8
  }
9
  return {}
10
}

Link to headingGet started with SvelteKit Auth

While SvelteKit Auth is still experimental, we’re excited about furthering the stability of the package and expanding Auth.js into other frontend frameworks besides Next.js.

We’d love to hear your feedback about which frameworks you’d like to see support for next. You can follow along with our progress on Twitter, or explore the new SvelteKit Auth package on GitHub. We’re actively working on new documentation as well.

Install @auth/sveltekit today and get started with our new SvelteKit Auth Template.

We’re incredibly thankful for the over 450 community contributors to NextAuth.js, including the core team of myself, Thang Vu, Nico Domino, Lluis Agusti, and Robert Soriano. We’d also like to thank Prisma, Clerk, Lowdefy, WorkOS, Checkly, Superblog, and others sponsoring NextAuth.js on OpenCollective. Finally, we’d like to thank the original creator of NextAuth.js, Ian Collins, for their work creating the base for all this innovation and Filip Skokan (@panva) for their outstanding work on open-source libraries.