This repo is now using main as the default branch.

Svelte + TS + Tailwind 2.2 app

This is a project template for Svelte apps. It lives at https://github.com/colinbate/svelte-ts-tailwind-template and is based on the official Svelte template with TypeScript pre-enabled and Tailwind CSS configured. Uses Tailwind CSS 2.1 with the JIT compiler enabled. The JIT feature is in preview and not tied to SemVer, so I've set it to 2.2.2 specifically.

Note that this isn't a SvelteKit app, this is a vanilla Svelte template with the above mentioned technologies pre-installed.

Important

The build/watch machanism has changed in TailwindCSS 2.2 and as such it does not seem to work properly with SveltePreprocess. If you use the legacy method it does work, and I've added an environment variable that does that when running the dev build. It won't work on Windows though and I will see about sorting that out as soon as I can. Setting TAILWIND_MODE=watch is what you need if you are on Windows. I will be attempting to get a better developer experience soon.

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

npx degit colinbate/svelte-ts-tailwind-template svelte-app
cd svelte-app

Note that you will need to have Node.js >=12.13 installed.

Get started

Install the dependencies...

cd svelte-app
npm install

...then start Rollup:

npm run dev

Navigate to localhost:5000. 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.

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

TypeScript has already been enabled in this template.