Code Repository Updates

It’s feasible to integrate the newest updates and features from SveltePak into your project.

However, it’s important to understand that each modification to your application complicates the process of updating your code base. This is due to the fact that you’re performing a rebase of your code onto the most recent version of SveltePak using Git.

Consequently, you’ll find yourself resolving merge conflicts and taking extra precautions to avoid overwriting your custom code.

To proceed with updating your code base, execute the command below:

git pull upstream main --allow-unrelated-histories --rebase

If you have any merge conflicts, you will have to resolve them manually. Once you’ve resolved all conflicts, you can continue the rebase process by executing the following command:

git rebase --continue

After the rebase process is complete, you can push your changes to your repository:

git push origin main

If you’re not comfortable with the rebase process, you can use the git merge command instead. However, this will create a merge commit, which can clutter your commit history.

To avoid this, we recommend using the rebase process. It’s a bit more complex, but it results in a cleaner commit history.

Update dependencies

After updating your code base, you should also update your dependencies. This can be done by executing the following command:

pnpm install

This will install the latest versions of all your dependencies, including SveltePak and its plugins.

Update your database

You may need to update your database schema after updating your code base. This can be done by executing the following command:

pnpm db:migrate

This will apply any pending migrations to your database, ensuring that your database schema is up to date with the latest version of your code base.