Usage of deprecated svelte-add in Tailwind manual installation parts of the get started doc

[AdiHarif]

Link to the Page

https://www.skeleton.dev/docs/get-started

Describe the Issue (screenshots encouraged!)

Hi!

Kinda new to Svelte and Tailwind, glad to try Skeleton for the first time :)

In the get started doc, the manual installation guide for tailwind suggests using svelte-add:

As svelte-add was merged to Svelte CLI and became deprecated, I would suggest changing this manual page to use Svelte CLI with the following command:

 npx sv add tailwindcss  

I used this command add tailwind (and later Skeleton) to an existing SvelteKit project and it seem to work just fine.

Would you like me to open a PR for this change?
Also let me know if I'm missing something :)

Thanks!

[endigo9740]

Hey @AdiHarif thanks for the heads up. Just so you're aware we're in a transitionary phase where we're about to drop a major release update, Skeleton v3. If you haven't already you can read more about it here:

• Announcement: Skeleton v3 Release Candidate 🎉 #3062
• Website: https://next.skeleton.dev/

We are potentially aiming to release this as soon as next week, so if you're just getting started we highly recommend you start with this. This will save you from a large migration in the near future.

Just note we are floating the idea of a delay to add Tailwind v4 support - which just launched this week as well!

• Status update for Skeleton v3 #3162

If you have any strong opinions on this, please feel free to vote. I'm so sorry for you to join at such a volatile time, but fingers crossed it's worthwhile for everyone! 🤞

[AdiHarif]

Thanks for the quick and informative response, it does seem I chose just the right time to hop on, isn't it :)

I will take a look at the RC, meanwhile will open a PR for the changes of v2 docs assuming it will still be available for the foreseeable future, regardless of the release date.

[endigo9740]

@AdiHarif just quick update - but it's occurred to me that we likely won't opt for sv for Skeleton v2 as it defaults to Svelte 5. While we do have kind of loose support for Skeleton v2 + Svelte 5, I can't say it's an ideal experience. There's some known issues we just won't have the resources to resolve before Skeleton v3 drops:

• Svelte 5 Migration Guide for Skeleton v2 #2887

Really though, this is one of the main goals of Skeleton v3 - we've built it to support Svelte 5 from the ground up. As such, if you prefer to stick with Svelte 5 (which we recommend), then your best bet is to start with Skeleton v3.

https://next.skeleton.dev/

The hard part here is whether you're ok with dealing with v3 being in a pre-release state. Plus it's looking highly likely we will implement a delay to Skeleton v3 this week to hold off until Tailwind v4 compatibility is added. Look for more announcements around this Monday.

That said, I've worked and operated as a frontend dev for 20 years now. I understand stability is a key to selecting tooling. So if Skeleton isn't landing where you need it right now, I can recommend these alternatives. They're all made be good people:

• https://www.melt-ui.com/ (also transitioning to Svelte 5)
• https://www.shadcn-svelte.com/ (also transitioning to Svelte 5)
• https://www.bits-ui.com/ (only Svelte 4 afaik) - same author as Shacn-Svelte
• https://flowbite.com/ and https://flowbite-svelte.com/ - though I'm unsure their status for Svelte 5 support

And yeah, it's a rough time to be in the Svelte/Tailwind world. Lots of big changes, but it'll be wonderful when the dust settles!

[AdiHarif]

Hi @endigo9740, Thanks for these informative and honest responses!
I appreciate you taking the time and effort to respond, especially considering you have some more urgent things to take care of with the complicated state of Skeleton v3.

I will continue experiment with the v3 RC for now, let me know if there is anything else I can assist with :)