skeleton VS realworld

Hi everyone, I'm so happy I can finally share the project I've been working on for the past few months. Ato UI is a themeable component UI library built with UnoCSS (with the Tailwind + Windi preset) and offers both styled and headless components, since the library is build on top of other fantastic headless libraries like Headless UI and Grail UI. Skeleton was also a big inspiration, as you'll be able to see in the designer page and the token system.

Vue 3 (with is quite close to Svelte in terms of DX, but Svelte has the edge here. Svelte is so simple, elegant and concise.<p>The biggest advantage of Vue is the ecosystem. However, Svelte is catching up. Some interesting UI component libs have recently arisen, e.g. <a href="https://skeleton.dev" rel="nofollow noreferrer">https://skeleton.dev</a>.<p>Performance wise, both are super fast.<p>Make sure to check out Sveltekit, even for building pure SPAs. The routing and data loading are worth it alone.

Should I use a framework independent library like DaisyUi or something related to svelte like flowbite-svelte or skeleton? Do I need svelte components? Should I build them by myself with DaisyUi?

I am using https://skeleton.dev for a dashboard and it is pretty amazing!

Hi, I've created a project with the skeleton.dev scaffolding tool:

To illustrate my concerns, let's take the "Real World Example" that was made by the official Svelte Team in the official repository (https://github.com/sveltejs/realworld).

I often end up looking at https://github.com/sveltejs/realworld when I want to check how SvelteKit apps are "supposed" to be built. It's maintained by the Svelte team so you can learn good practices there.

I was looking at this a couple of hours ago and took a look at the realworld app app. I found all the fetch is done through the api, which is always called from server side. Even for user interaction, they always use forms to send the requests through the server.

I was looking at the realworld example and noticed that to login, they send a POST request to auth/login. auth/login then puts the data in an user object and sends it to an external API.

I'm pretty sure fetch is available for endpoints in latest version of svelte kit (older versions of svelte kit need to use node-fetch, updated svelte real world app has removed it as a dependency) but it's not working for me. Overview of my project files is below:

I’d recommend to take example from real world Svelte https://github.com/sveltejs/realworld