Svelte setup example not working

First issue: Running "dev": "run-p start:dev autobuild watch:build" results in ERROR: Task not found: "watch:build". Changing watch:build to --watch:build fixes this.

Second issue: To see the result of applying tailwind classes live in the browser, everything needs to be rebuilt by running the build script—I assume that's not the intended behavior.

[mayashavin]

@Dyslexicon or you can change it to "watch:tailwind". it will also work.

[rlaferla]

I'm running into problems with it. For one, it shouldn't say that it's "really simple" because it really isn't -- just to set expectations. There also needs to be mention of "npm-run-all" being required.

There is an article which shows how to set up Svelte with Tailwind that I used to great effect. I would update the readme to reflect that and make a pull request, but it doesn't seem like this repo is being monitored. So, here is the article: Using TailwindCSS with SvelteJS.

[quantuminformation]

Is the svelte example the same as you can use with Sapper?

@quantuminformation I believe the setup in the article I linked would work similarly with Sapper. Only one way to find out...

[quantuminformation]

This worked for me:

jakobrosenberg/sapper-tailwindcss-starter-minimal@5ae1ba0

[heliosnarcissus]

i got frustrated following the instructions I almost punched my monitor in.
especially it didnt mention you need to instal npm-run-all , had to Google the errors in my terminal . NPM RUN DEV doesnt work either.

Here's how you write a tutorial:
ACTUALLY START FROM SCRATCH AND FOLLOW WHAT YOU WROTE!!!!

[pascalandy]

One day I'll find the stack ... one day ...

Stack

I'm looking to build landing page (not a blog)

• TailwindCSS V2
• Svelte with a 3 pages template so I can understand the relations between the pages
• AlpineJS
• Easy to copy-paste TailwindUI examples
• yarn && yarn dev && yarn build

optimizations I expect

• purge css
• minified css/html/js
• image compression / resize to responsive key points
• image easy loading
• Lighthouse 100%, and more stuff that a framework should care for :)

CI

then CI everything via Github Actions (that's the part I'm good at) + CD