a4d94f522a
Some checks failed
CI / Backend (push) Failing after 11s
CI / UI (push) Successful in 51s
Release / Test backend (push) Successful in 54s
Release / Check ui (push) Successful in 1m9s
CI / Backend (pull_request) Successful in 45s
CI / UI (pull_request) Successful in 56s
Release / Docker / caddy (push) Successful in 1m22s
Release / Docker / backend (push) Failing after 1m46s
Release / Docker / ui (push) Successful in 2m32s
Release / Docker / runner (push) Successful in 3m35s
Release / Gitea Release (push) Has been skipped
- ui/src/error.html: custom SvelteKit last-resort fallback (replaces the bare '500 | Internal Error' shown when +error.svelte itself fails) — branded, auto-refreshes in 20s, book+lightning SVG illustration - ui/src/routes/+error.svelte: improved with context-aware SVG illustrations (question mark book for 404, lightning bolt for 5xx), larger status watermark, and a Retry button on non-404 errors - caddy/errors/500.html: new static error page matching the 502/503/504 design — served by Caddy when a gateway-level 500 occurs - Caddyfile: add handle_errors 500 block pointing at /srv/errors/500.html - caddy/Dockerfile: COPY errors/ into image so static pages are baked in
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.