package names

[Hugos68]

At some point I would like to rethink how we name our packages, we have a whole lot of skeleton with no meaning. I think we should rename our packages at some points as following:

@skeletonlabs/skeleton -> @skeletonlabs/tailwindcss
@skeletonlabs/skeleton-svelte -> @skeletonlabs/svelte
@skeletonlabs/skeleton-react -> @skeletonlabs/react
@skeletonlabs/skeleton-common -> @skeletonlabs/shared

@endigo9740 How do you feel about this?

[endigo9740]

@Hugos68 the names were settled on to leave the door open if Skeleton Labs introduces other products in the future. Floating UI Svelte would have been an example of this. We might have eventually introduced a Vue or Solid version to match:

@skeletonlabs/floating-ui-svelte
@skeletonlabs/floating-ui-vue
@skeletonlabs/floating-ui-solid

So I'd very much like to keep the names as is.

As per the core package, while it does use Tailwind, I don't think dubbing it like a component package would be quite right. It's an equivalent comparison. Keep in mind it's the only package that can be used standalone too because it's a full product unto itself. Our framework packages contain a set of components for that framework. While our core package contains:

• Global styles
• Animations
• Themes
• Utility Classes
• Variants

It basically shapes the "design system framework". If were going to give it a more semantic name "design system" would be closer than Tailwind. Tailwind just happens to be the tool we've built this on in this case. And will be further developed in v5+

Personally I'm very pleased with the current package names. If we ever decide to go all in on ONLY Skeleton forever, then some of those changes might make sense. But for now, I do't think this will be something we move forward with.