Psst — looking for a more complete solution? Check out SvelteKit, the official framework for building web applications of all sizes, with a beautiful development experience and flexible filesystem-based routing.

Looking for a shareable component template instead? You can use SvelteKit for that as well or the older sveltejs/component-template

First 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.

If you face problem when running, Please create the app using the following command

npx degit github:actionanand/first-svelte#1-skeleton your-app-name
cd your-app-name

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

Other Resources

• Replacement for git clone - degit
• npm-run-all NPM Package
• Images with Lorem.space - placeholder image generator
• Building Svelte micro frontends with Podium
• CTO’s guide to Svelte – what can the rising frontend framework do for you?
• What I Like About Writing Styles with Svelte
• 5 things I love about Svelte
• Why Svelte is different - and awesome!
• The Svelte Handbook
• Use Svelte with SASS/SCSS in VSCode (example + cloneable repo)
• How to use scss with Svelte?

Useful Resources & Links

1. Official Docs (if)
2. Official Docs (each)
3. Official Docs (keys)
4. Event Modifier
5. Svelte Lifecycle hooks tutorial
6. The Component Lifecycle in Svelte
7. Svelte Component Lifecycle Hooks
8. How to deploy a React, Angular and Vue project to Github pages
9. Deploying a Svelte Application to Github Pages
10. Publishing on Github Pages

    Don't forget to prefix paths in html file with . before deployment.