64cd2b8add
CI-build hat mit "Some specified paths were not resolved, unable to cache dependencies" abgebrochen, weil actions/setup-node@v4 mit cache: 'npm' eine committed package-lock.json erwartet. Lockfile war bisher in app/.gitignore ausgeschlossen — ungewoehnliche konvention fuer SvelteKit-projekte; reproduzierbare builds (sowohl CI als auch fresh-clone) brauchen den lockfile. Jetzt committed, mit dem stand der nach den isomorphic-dompurify+@types/node-installs existiert. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .vscode | ||
| src | ||
| static | ||
| tests | ||
| .env.example | ||
| .gitignore | ||
| .npmrc | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| svelte.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
README.md
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.15.1 create --template minimal --types ts --install npm .
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.