svelte-adders VS sveltekit-starter

Perhaps your tool can steal some inspiration from the following:

- svelte-add is a similar tool for Svelte(Kit) projects: https://github.com/svelte-add/svelte-add

- svelte-add was originally based on a more generic tool: https://preset.dev

- I actually find `npm create svelte@latest` sufficient most of the time. It's like a starter project with presets for most best practices.

Oof... Not gonna lie, that one looks rough. I would start with something simpler to get started with. Maybe pick one from here https://github.com/svelte-add/svelte-add

For this tutorial, I’ll show you how to use a utility package named svelte-add to handle the integrations.

If you're just learning SvelteKit, check this tool out: https://github.com/svelte-add/svelte-add

It will save you a ton of time by making it really easy to add integrations to your projects (like Tailwind, Bootstrap, Supabase, Jest, etc)

By the way svelte-add is a great tool to quickly add Tailwind and a bunch of useful tools to a project. Highly recommended! I'm always starting new projects to experiment and this thing saves me a lot of time.

Somewhat the documentation is confusing, IMHO. Maybe it is just me, however there is just too much configuration to be done. I've never figured out how to actually make it work after the latest release 0.7. Would love to have Houdini+KitQL in https://github.com/svelte-add/svelte-add . Just run a simple command like npx svelte-add@latest houdini-kitql with a prompt for graphql URL and done. All the configs added automagically

We'll use SvelteAdd to add TailwindCSS to our application quickly. Run the below command to add TailwindCSS to our project.

I've created a couple of example projects using the npm init command for both Vite and Svelte. Added in Tailwind support using Svelte Add and replaced the index page styles on each with Tailwind styles.

I had this on my starred repos, I hope you find it useful!

For Endpoints, I'd recommend checking out this example for a good idea on how they're used. If you're gonna be transforming the external API data, you can do it in the Endpoint. Speed really hasn't been a concern for me, even deployed on Cloudflare Workers. Here's one of my endpoints, for an example of how I use and abuse endpoints lmfaoo.

I saw that but it's not really designed for component libraries. It's also SSR. I'm looking to do client side rendering. Really good template though. Will probably take inspiration from it when moving past components.