| runme | ||||
|---|---|---|---|---|
|
This is a Sveltekit Auth Project. An example website is currently deployed here. It is an open source auth starter project utilizing Lucia for authentication, shadcn-svelte for ui elements, Lucide for icons, Prisma for database connectivity and type safety and Sveltekit for the javascript framework. I also used Zod and Superforms to handle form validation and management. It has email verification, password reset, and will send an email if the user changes their email address to re-verify it. It is released as open source under an MIT license.
While creating this project, I made use of several great videos and tutorials from Huntabyte (who also developed the svelte port for shadcn) and Joy of Code. Both have great tutorials for all things related to Sveltekit.
This project creates an email and password user log in system and is my attempt to make something production ready with all of the usual features you expect. You can create new users and sign them in. It has user roles. It will verify a users email address. You can edit your profile including changing your email address and password. You can reset your password in case you forgot it. You can also change themes and have a light and dark mode. I didn’t see any examples utilizing these frameworks that had all of these necessary features.
It has a logging system for errors which I have tracked in Axiom. I wrote a separate article about the logging system here.
I picked Lucia for auth because it had great documentation and seemed to be in active development and was very full featured. It can provide authentication for OAuth providers as well. I always want to have a fallback for email and password, so that is what I chose to make for this project.
shadcn-svelte is another great project with a really nice development experience. It has beautiful ui elements that are very easy to use.
Prisma is another great package and it is used for database connectivity and type safety. It works with many databases so it’s easy to change your database with one line of code. It has an easy to use ORM that cuts back on the amount of code you need to write.
Zod is a typescript schema validation that allows you to easily validate your input in projects. It is very easy to setup what your data should look like to validate against.
Finally Superforms makes it easy to work with forms in Sveltekit. It cuts down a lot on boilerplate code when working with forms.
This was the first time working with many of these packages, but they really do streamline much of the Sveltekit development process. If there are any mistakes, please open up an issue on the project. Also I was pleasantly surprised at the scores from Google PageSpeed Insights. This project scored a 100% in all metrics.
sample.env — private environmental server side variables that must be set. Rename to.env and supply your personal project settings.
/prisma/schema.prisma — holds the prism schema which is the design of your data in the app and db. Currently holds the auth schema for Lucia auth.
app.d.ts — holds type definitions for lucia and can hold your additional types for other features.
hooks.server.ts — holds a Lucia auth handle function.
theme.postcss — holds a custom theme for skeleton. This can be set in /routes/+layout.svelte. Comment out the theme-skeleton and add in theme.postcss. You can create your own custom theme https://www.skeleton.dev/docs/generator. There are also lots of premade themes included with sveltekit. To use those, change theme-skeleton.css to theme-modern.css or another theme name.
convertNameToInitials.ts — function for making initials from first and last name of user for the avatar.
/logo — used as the logo throughout the app.
/navigation — navigation menu links used in /routes/+layout.svelte. They change based on whether user is logged in or not.
/ui - our shadcn ui components. Contains many components related to that.
constants.ts — all of the public constants that do not need to be hidden server side. I prefer this to naming constants PUBLIC_WHATEVER in the .env file, which is another option. I prefer to keep my .env file with only server side env variables.
email-messages.ts — this is where I keep all of the email messages that need to be sent. It makes it easier in case changes need to be made to the emails that are sent out.
prima.ts — file used to initialize the prisma client.
zod-schemas.ts — holds the schema used in zod. This defines how our form data needs to be validated.
email-send.ts — this handles our email sending with AWS SES. It only runs server side to keep your credentials hidden.
lucia.ts- this initializes the lucia-auth package for handling our auth functions. It also holds the extra custom fields we added to the user.
log.ts- special log routine to provide debug info about our app.
+layout.server.ts — gets the user info from lucia-auth if available so we can access it in our app.
+layout.svelte — overall site layout which is inherited by the rest of our app.
+page.svelte-basic info about our app
+error.svelte-error message for problem routes.
Holds our terms and conditions page. Do not use this for your own website as I just used ChatGPT to make this. You should consult a legal professional to develop the terms for your own app.
Holds our privacy policy page. Do not use this for your own website as I just used ChatGPT to make this. You should consult a legal professional to develop the privacy policy for your own app.
This holds the password reset form and function to send a password reset email when the user enters there email address,
This allows the user to actually put in the new password, the token comes from the email from the users reset request. Anything in [] is able to be accessed as a parameter in Sveltekit, so [token] can be accessed via (token = event.params.token).
This is the message the user sees if there reset was successful.
This allows the user to update their profile with new information. If they change their email address we also un-verify them and send them an email asking them to reconfirm their email. We also send an email to their old address telling them this change was made with the old and new address so that the data can be reset manually if the users account was hacked.
Page and functions for signing in the user.
Function for signing out the user.
Page and functions for signing up the user.
This page asks user to check there email and verify it.
This page confirms the email address by verifying the token the user received in his email account.
This resends the verify email in case the user didn’t receive or lost the email.
This route group is only allowed to be accessed when a user is logged in.
Hopefully you may find some of this code useful for your own project. Please feel free to use it in any project.