f9a4a0e416
Some checks failed
CI / Backend (push) Failing after 11s
CI / UI (push) Successful in 45s
Release / Test backend (push) Successful in 53s
Release / Check ui (push) Successful in 1m3s
Release / Docker / caddy (push) Successful in 55s
CI / Backend (pull_request) Successful in 48s
Release / Docker / backend (push) Failing after 11s
Release / Docker / runner (push) Failing after 11s
CI / UI (pull_request) Successful in 50s
Release / Docker / ui (push) Successful in 2m20s
Release / Gitea Release (push) Has been skipped
The paraglideVitePlugin runs at build time (buildStart hook) and fetches the inlang plugin from cdn.jsdelivr.net to recompile messages. This: 1. Overwrites messages.js with 'export * as m from ...' unconditionally 2. Causes Rollup SSR tree-shaking to replace all m.*() calls with (void 0) 3. Crashes every page server-side with 'TypeError: (void 0) is not a function' The plugin is no longer needed: compiled paraglide output is committed to git and updated via 'npm run paraglide' when messages change. Removing the plugin lets Vite treat messages.js as a plain static module, keeping all exports intact through the SSR bundle.
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.