Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1,154 changes: 1,154 additions & 0 deletions apps/svelte.dev/content/docs/kit/50-reference/10-configuration.md

Large diffs are not rendered by default.

15 changes: 15 additions & 0 deletions apps/svelte.dev/content/docs/kit/50-reference/20-cli.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't touch on this yet, but all the 50-reference Kit docs shouldn't be synced for now / be left out. They are duplicative to the new 98-reference which I have lying around locally. I should push them up to a branch (can't merge to SvelteKit main because that would rebuild the existing kit.svelte.dev)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: Command Line Interface
---

SvelteKit projects use [Vite](https://vitejs.dev), meaning you'll mostly use its CLI (albeit via `npm run dev/build/preview` scripts):

- `vite dev` — start a development server
- `vite build` — build a production version of your app
- `vite preview` — run the production version locally

However SvelteKit includes its own CLI for initialising your project:

## svelte-kit sync

`svelte-kit sync` creates the `tsconfig.json` and all generated types (which you can import as `./$types` inside routing files) for your project. When you create a new project, it is listed as the `prepare` script and will be run automatically as part of the npm lifecycle, so you should not ordinarily have to run this command.
Loading
Loading