Fullstack Example with SvelteKit Actions and Load Functions

git clone https://github.com/GlistenSTAR/prisma_sveltekit_postgresql_pnpm.git template```
cd template
pnpm install

- Create and seed the database

Run the following command to create your SQLite database file. This also creates the User and Post tables that are defined in prisma/schema.prisma:

npx prisma migrate dev --name init

When npx prisma migrate dev is executed against a newly created database, seeding is also triggered. The seed file in prisma/seed.ts will be executed and your database will be populated with the sample data.

- Start the app

pnpm run dev

The app is now running, navigate to http://localhost:5173/ in your browser to explore its UI.

Using the SvelteKit Actions and Load functions

The load functions interact with the server to get data into your pages while the actions function mutates your data. Both these functions are defined in the +page.server.ts in the respective route folders.

LOAD

• /: Fetch all published posts
• /drafts: Fetch all drafted posts
• /p/:id: Fetch a single post by its id

ACTIONS

• /create: Create a new post
  • default action body:
    • title: String (required): The title of the post
    • content: String (required): The content of the post
    • authorEmail: String (required): The email post's author
• /p/:id:
  • publishPost action: Publish a post by its id
  • deletePost action: Delete a post by its id
• /signup: Create a new user
  • default action body:
    • email: String (required): The email address of the user
    • name: String (required): The name of the user

- Evolving the app

Evolving the application typically requires three steps:

1. Migrate your database using Prisma Migrate
2. Update your server-side application code
3. Build new UI features in Svelte

For the following example scenario, assume you want to add a "profile" feature to the app where users can create a profile and write a short bio about themselves.

1. Migrate your database using Prisma Migrate

The first step is to add a new table, e.g. called Profile, to the database. You can do this by adding a new model to your Prisma schema file file and then running a migration afterwards:

// schema.prisma

model Post {
  id        Int     @default(autoincrement()) @id
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields: [authorId], references: [id])
  authorId  Int
}

model User {
  id      Int      @default(autoincrement()) @id 
  name    String? 
  email   String   @unique
  posts   Post[]
+ profile Profile?
}

+model Profile {
+  id     Int     @default(autoincrement()) @id
+  bio    String?
+  userId Int     @unique
+  user   User    @relation(fields: [userId], references: [id])
+}

Once you've updated your data model, you can execute the changes against your database with the following command:

npx prisma migrate dev

2. Update your application code

You can now use your PrismaClient instance to perform operations against the new Profile table. Here are some examples:

Create a new profile for an existing user

const profile = await prisma.profile.create({
  data: {
    bio: "Hello World",
    user: {
      connect: { email: "[email protected]" },
    },
  },
});

Create a new user with a new profile

const user = await prisma.user.create({
  data: {
    email: "[email protected]",
    name: "John",
    profile: {
      create: {
        bio: "Hello World",
      },
    },
  },
});

Update the profile of an existing user

const userWithUpdatedProfile = await prisma.user.update({
  where: { email: "[email protected]" },
  data: {
    profile: {
      update: {
        bio: "Hello Friends",
      },
    },
  },
});

3. Build new UI features in Svelte

Once you have added a new route to your app (e.g. /profile/+page.server.ts with respective load and action operations), you can start building a new UI component in Svelte. It could e.g. be called /profile/+page.svelte and would be located in the src/routes directory.

In the application code, you can manipulate data using actions and populate the UI with the data you receive from the load function.

Switch to another database (e.g. PostgreSQL, MySQL, SQL Server, MongoDB)

If you want to try this example with another database than SQLite, you can adjust the the database connection in prisma/schema.prisma by reconfiguring the datasource block.

Learn more about the different connection configurations in the docs.

datasource db {
  provider = "postgresql"
  url      = "postgresql://USER:PASSWORD@HOST:PORT/DATABASE?schema=SCHEMA"
}

datasource db {
  provider = "postgresql"
  url      = "postgresql://janedoe:mypassword@localhost:5432/notesapi?schema=public"
}

datasource db {
  provider = "mysql"
  url      = "mysql://USER:PASSWORD@HOST:PORT/DATABASE"
}

datasource db {
  provider = "mysql"
  url      = "mysql://janedoe:mypassword@localhost:3306/notesapi"
}

datasource db {
  provider = "sqlserver"
  url      = "sqlserver://localhost:1433;initial catalog=sample;user=sa;password=mypassword;"
}

datasource db {
  provider = "mongodb"
  url      = "mongodb://USERNAME:PASSWORD@HOST/DATABASE?authSource=admin&retryWrites=true&w=majority"
}