Based on basic svelte examples: https://svelte.dev/examples/spread-props

svelte app

This is a project template for Svelte apps. It lives at https://github.com/sveltejs/template.

To create a new project based on this template using degit:

npx degit sveltejs/template svelte-app
cd svelte-app

Note that you will need to have Node.js installed.

Get started

Install the dependencies...

cd svelte-app
npm install

...then start Rollup:

npm run dev

Navigate to localhost:8080. You should see your app running. Edit a component file in src, save it, and reload the page to see your changes.

By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv commands in package.json to include the option --host 0.0.0.0.

If you're using Visual Studio Code we recommend installing the official extension Svelte for VS Code. If you are using other editors you may need to install a plugin in order to get syntax highlighting and intellisense.

Building and running in production mode

To create an optimised version of the app:

npm run build

You can run the newly built app with npm run start. This uses sirv, which is included in your package.json's dependencies so that the app will work when you deploy to platforms like Heroku.

Single-page app mode

By default, sirv will only respond to requests that match files in public. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.

If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start" command in package.json:

"start": "sirv public --single"

Using TypeScript

This template comes with a script to set up a TypeScript development environment, you can run it immediately after cloning the template with:

node scripts/setupTypeScript.js

Or remove the script via:

rm scripts/setupTypeScript.js

If you want to use baseUrl or path aliases within your tsconfig, you need to set up @rollup/plugin-alias to tell Rollup to resolve the aliases. For more info, see this StackOverflow question.

Deploying to the web

With Vercel

Install vercel if you haven't already:

npm install -g vercel

Then, from within your project folder:

cd public
vercel deploy --name my-project

With surge

Install surge if you haven't already:

npm install -g surge

Then, from within your project folder:

npm run build
surge public my-project.surge.sh

File name changes

The router is now folder-based, not file-based. This means there's now only one way to describe a route.

Here's how you define that there's a route /about:

Old	New
routes/about/index.svelte	routes/about/+page.svelte
routes/about.svelte	routes/about/+page.svelte

The same principle applies to parameterized routes:

Old	New
routes/[slug]/index.svelte	routes/[slug]/+page.svelte
routes/[slug].svelte	routes/[slug]/+page.svelte

The naming of the routing files has changed. They correspond as follows (assuming the first variant of the table above):

Old Description	Old	New
page UI	index.svelte	+page.svelte
load function etc	<script context="module"> in index.svelte	+page.js
page endpoint	index.js with index.svelte next to it	+page.server.js
standalone endpoint	index.js without index.svelte next to it	+server.js
layout UI	__layout.svelte	+layout.svelte
load function etc	<script context="module"> in __layout.svelte	+layout.js
		+layout.server.js (server GET for layout, didn't exist previously)
error UI	__error.svelte	+error.svelte
load function etc	<script context="module"> in __error.svelte	No longer exists

To summarize: All route files have a + sign in front now to distinguish them at a glance and group them, the contents of <script context="module"> is moved into a separate file, which means that there's now at most three files per page (or layout).

</tbody>