Svelte Vite Starter

From here. With jest and router added

A starter template for Svelte that comes preconfigured with Vite, TypeScript, SCSS, Babel, Autoprefixer, and HMR.

• Svelte Vite Starter
  • Getting started
    • Installation
    • Starting the development server
    • Building for production
  • Usage
    • Global stylesheets
    • Browsers list
    • Babel customization
    • Source maps in production
    • Import path aliases

⚠ Consider trying the new vite-based SvelteKit!

---

Getting started

Installation

Pull the template files with degit and install dependencies.

npx degit baileyherbert/svelte-vite-starter
npm install

Starting the development server

Run the dev script to start a live development server with hot module replacement. Then check the output for a link to the app, which is usually http://localhost:5000/:

npm run dev

Building for production

Run the build script to bundle the app for production. The bundle will be created at /dist/assets/ and the dist directory will contain all files you need to host the app:

npm run build

💡 Tip: You can quickly test the production build by running npm run preview locally.

---

Usage

Global stylesheets

Edit the index.html file and add additional <link> references to stylesheets:

<link rel="stylesheet" type="text/css" href="/src/styles/index.scss" />

You can specify css, scss, and sass files here, and they will be compiled and minified as necessary. These styles will be added to the bundle in the order specified. Svelte's styles will always load last.

💡 Note: The paths to these assets must start with / in order to resolve.

Browsers list

The bundle will be compiled to run on the browsers specified in package.json:

"browserslist": [
    "defaults"
]

If you wish to customize this, please refer to the list of example browserslist queries.

Babel customization

Production builds are compiled with Babel automatically. If you wish to disable it, edit the vite.config.ts file:

const useBabel = false

Source maps in production

Source maps are generated automatically during development. They are not included in production builds by default. If you wish to change this behavior, edit the vite.config.ts file:

const sourceMapsInProduction = true

Import path aliases

Define import path aliases from the tsconfig.json file. For example:

"paths": {
    "src/*": ["src/*"],
    "@stores/*": ["src/stores/*"]
}

You can then import files under these aliases and Vite will resolve them. Your code editor should also use them for automatic imports:

import { users } from '@stores/users' // src/stores/users.ts

The root directory is configured as a base path for imports. This means you can also import modules with an absolute path from anywhere in the project instead of using a large number of .. to traverse directories.

import { users } from 'src/stores/users'