every blog needs subheader text

Sveltekit with TailwindCSS

Table of contents.

I wanted to learn how to setup a simple interactive website, and react is so 2019 and verbose, so I looked around and svelte looked awesome, especially the tutorial which is a work of art.

Svelte is a JS framework which puts html, css and javascript inside a .svelte file. It aims to stick mostly to basic html/css/js, so is easier to use than the more complicated frameworks like react which essentially are their own language. A good intro video.

Each .svelte file can be thought of as a component, and you use them like lego to build an app. A very basic svelte file is just js, html and css - try it out in the svelte repl. A sample component (i.e a svelte file to be reused elsewhere) looks like:

<!-- saved as nested.svelte -->
    export let a_variable = "you can pass in your own value!";

<h2>nested h2</h2>

<p>This is a 1em paragraph, orange in nature, with this passed in beauty: <strong>{a_variable}</strong>.</p>

  p {color: orange; font-size: 1em;}
    h2 {color: teal; font-size:1.5em;}

The main entry point would be called App.svelte and will have javascript, html and css like so:

<!-- svelte is mostly 100% javascript -->
    import Nested from './nested.svelte';
  let name = "KO";
  let img = ""

<!-- content goes here, curly brackets are javascript -->
<h1>Hello {name.toUpperCase()}!</h1>
<p>we be coding</p>

<!-- import and use a component -->

<!-- we can pass in values to the component, even computed ones -->
<Nested a_variable={21*2}/> 

<img src={img} alt="alt text">

<!-- css goes here, scoped only to this file -->
  h1 {color: purple}

While it’s possible to build an entire app inside a single .svelte file, we’re better off with making multiple components each doing one thing and import them as needed, as in the example above.

Thats the basics of svelte! Its actually pretty straightforward. For simple apps, this is all you need, but for more complex apps you need a router, which is where sveltekit comes in.


Sveltekit is a framework for svelte which transforms svelte files into a static or interactive web app.

Pages (or routes)

Sveltekit uses a file based router, which is fancy speak for saying it looks at the folder src/routes and turns every svelte file into a page.  The entry point of the app is src/routes/index.svelte.

So, src/routes/about.svelte becomes the /about page, or alternatively, if the about page refers to other files and stuff, we can put all in a sub directory: src/routes/about/index.svelte to keep them contained.


i.e shared components, like a header visible on each page. This file applies to ever page: src/routes/__layout.svelte. Layouts can be nested, so subfolders can contain a __layout.svelte file which only applies to the pages in that subfolder.

Put __layout.reset.svelte in any subfolder where you don’t want the pages to inherit layouts.

sveltekit targets

Sveltekit sites can run on node server, or be pre-rendered to to run on any web server as static web pages. The following two adapters seem production ready:

These two are listed as experimental:


Css has become so complex that using it directly is akin to programming in C. So there are a ton of css frameworks which do the heavy lifting. But all of them require separating the content (html) from design (css), and going back and forth can be a pain.

Tailwind provides a ton of helper styles to use directly inside html. This makes it easier to just modify things directly all in one file. This made sense to me with svelte as that puts content, code and style all in the one svelte file anyways.

To see more about tailwindcss, see this earlier blog post.

Setting up all the things

This is the complex part. So I’m laying it out here step by step for my future self.

To see this in action, here's the github repo for this starter project and the final, super simple output site.

  1. install node using brew (mac) or nvm (cross platform, probably better) or fnm.
  2. install VS code and these extensions:
    1. svelte vs code
    2. tailwindcss

Note: tailwindcss wasn't auto-completing so I had to update this vscode setting:

"editor.quickSuggestions": {
  "strings": true

Install svelte and tailwind

See sveltekit docs and svelte-add for more.

npm init svelte@next myapp
cd myappp
npx svelte-add tailwindcss --jit
npm install

The install script asks for options, I choose:

This will have installed and configured sveltekit and tailwindcss. To run:

npm run dev -- --open

Additionally, add the --host flag to expose the site to the local network, handy for testing it on your phone and other computers. If on a laptop, since the page reloads automagically on change, you can prop up an ipad or something with the output open.

Optionally, add the tailwind typography plugin:

npm install -D @tailwindcss/typography

and update the plugins section in tailwind.config.js to include this:

plugins: [

Then start the site: npm run dev -- --open. Presto! A svelte site powered by sveltekit and tailwindcss should be up and running. Go to src/routes and open index.html and copy paste this below whats already there:

<article class="prose px-8 py-4 bg-gray-200">
    <h1>Welcome to SvelteKit</h1>
    <p>Visit <a href=""></a> to read the documentation</p>

If the above chunk is styled, and updates in the browser preview, then everything is setup fine and working.


Time to setup an adaptor to publish this to the web. Initially I tried adaptor-static to deploy to github pages, but kept running into errors. Now the simplest thing is to build the static site locally, and use github pages to deploy the already built site, but this requires a working local dev env for any changes and thats so last year.

So I went with the vercel adaptor - this worked pretty painlessly out of the box, since essentially there is no local build step - you just run a local dev server: npm run dev -- --open to develop, and push to github once done.


The exciting part about using vercel to deploy is how easy it is:

Vercel detects the following frontend frameworks automatically and chooses the best default settings for you.

Install the adaptor:

npm install -D @sveltejs/adapter-vercel@next

Update svelte.config.js so it has the vercel adapter line:

    kit: {
    adapter: vercel(),

Then go to vercel, start a new project and point it to the repo for this starter project. The default settings should just work - it should build and publish the site, and auto-rebuild and publish on every git push.

The final output:

To look at later

posted , updated
tagged: webdev View on: github