svelte-adders VS changesets

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.

In my circles, this is the go-to for release automation / changelogs: https://github.com/changesets/changesets

🦋 Publicando com changesets

Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.

Doing these tasks by hand can quickly become a hassle. If you're open to receiving contributions from others, it can be an even bigger headache. In this post we'll cover how to use changesets to automate all of these steps.

For versioning we use changeset, but with fixed-packages. We have found that the user thinks updating and managing our dependencies much easier if they can just bump each package to the same version. (storybook, sanity follows this appoach). While it feels unintuitive that each package gets a major if just the CSS has breaking changes, the user don't really care. They just want to finish the chore of updating their dependencies fast, without having to understand the system that deeply. This also makes documenting the changes much easier!

Thanks for sharing this. Why should I choose that instead of Changesets that work like a charm?

You’re right this information would be better suited for for commit trailers. A lot more information can be put there as well. For the purpose of changelog generation, what it’s commonly used for, it could just as well be put in the trailers and not crammed into the subject. I personally prefer changesets though.