About Tailwind v4

[nataniel]

Link to the Page

https://next.skeleton.dev/docs/get-started/installation/vite-svelte

Describe the Issue (screenshots encouraged!)

It should clearly state here, that Skeleton v3 does not work with Tailwind v4. It would save a lot of people a lot of work trying to figure this out! :)

[endigo9740]

@nataniel We have numerous posts talking about our ongoing effort to support Tailwind v4:

• Skeleton v3 has been delayed #3175
• Tailwind v4 Support - RFC and Status Update #3192
• Tailwind v4 and RFC Follow Up #3211

This has required a total rewrite of our core package, which we're actively working on. We had already updated the page you linked to to pin to Tailwind v3. If you are following our guide, you should not be installing a version of Tailwind v4:

If you update your project outside of that, there's not much we can do prevent that. I understand another warning would help with education here, but not sure if the team and I have the bandwidth to jump on this before we have the update up and out the door.

Maybe consider submitting a PR if you think this would be constructive?

[nataniel]

This code:
npm install -D tailwindcss postcss autoprefixer

currenly installs tailwindcss 4.0.6 and following the guide results in error:
[plugin:vite-plugin-svelte] Error while preprocessing /home/nataniel/projects/my-skeleton-app/src/App.svelte - [postcss] It looks like you're trying to use tailwindcssdirectly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install@tailwindcss/postcss and update your PostCSS configuration.

If you just change it to:
npm install tailwindcss@3

it works correctly (if you don't want to add a warning).

Unfortunately, I'm very new to tailwind, I don't think I will be able to submit a PR :)
Thanks for your great job!

[endigo9740]

I see. Honestly we may have Tailwind v4 support rolled out before we get a chance to append this. So thanks for the heads up, but again not sure if there's anything we can do in the meantime.

I've tagged this as a bug I'd welcome a PR from anyone willing an able to fix this for BOTH Vite onboarding guides.