Manuel
Manuel
This is supported by `svelte-add`s successor [`svelte-compose`](https://svelte-compose.com/) [Bootstrap composer](https://svelte-compose.com/composer/bootstrap/)
Thanks for your contribution! Could you enlighten me under which circumstances this was not working properly? Because I'm pretty sure this was working this weekend and the last pipeline runs...
Thanks for your input! I'm honestly not sure what is the correct way to implement this. I tried searching for best practices inside the docs, but I was unable to...
Based on the feedback we got, it looks like you made the right call! I have adapted the other adders as well, and I'm going to merge once the tests...
Initially brought up by @tburny in https://github.com/svelte-compose/svelte-compose/issues/23
Initially brought up by @tburny in https://github.com/svelte-compose/svelte-compose/issues/22
This is an upsteam bug. I have created an issue in the storybook github.
The problem I see with ```sh npx @svelte-add/tailwindcss@latest --typography --forms ``` is that this ```sh npx @svelte-add/tailwindcss@latest ``` would implicitly assume that all options are false / fallback to the...
Absolutely true! What would be your preferred way? I think I would personally prefer the first way with `const config: Config = { ... }`. According to https://astexplorer.net/ this should...
This probably happened when creating a completely new project and applying an adder immediately, or was there another use case?