All checks were successful
Release / Test backend (push) Successful in 41s
Release / Check ui (push) Successful in 45s
Release / Docker / caddy (push) Successful in 45s
Release / Docker / backend (push) Successful in 2m53s
Release / Docker / runner (push) Successful in 2m34s
Release / Docker / ui (push) Successful in 1m56s
Release / Gitea Release (push) Successful in 20s
The save-settings $effect was firing on the initial data load because settingsApplied was set to true synchronously in the apply effect, then currentTheme/fontFamily/fontSize were written in the same tick — causing the save effect to immediately fire with uninitialized default values (theme: "", fontFamily: "", fontSize: 0), producing a 400 error. - Add settingsDirty flag, set via setTimeout(0) after initial apply so the save effect is blocked for the first load and only runs on real user-driven changes - Also accept empty string / 0 as 'not provided' in PUT /api/settings validation as a defensive backstop
sv
Everything you need to build a Svelte project, powered by sv.
Creating a project
If you're seeing this, you've probably already done this step. Congrats!
# create a new project
npx sv create my-app
To recreate this project with the same configuration:
# recreate this project
npx sv@0.12.4 create --template minimal --types ts --install npm ui
Developing
Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:
npm run dev
# or start the server and open the app in a new browser tab
npm run dev -- --open
Building
To create a production version of your app:
npm run build
You can preview the production build with npm run preview.
To deploy your app, you may need to install an adapter for your target environment.