J
J
Setting up GitHub Actions would be an option for each adder since how it's expected to work depends on the deployment target.
(When we have other deployment adders, I'll apply their labels to this issue)
You're right, we could update `svelte-add` to accommodate object syntax for plugins in the PostCSS config.
Here's what I'm currently thinking without doing extra research: I am in the process of setting up the framework for detectors, with `postcss`'s being written already: https://github.com/svelte-add/svelte-add/blob/15ed8b50ac13c27ed6b6dec010486db67e2c1840/projects/svelte-add/adders/postcss/detect.js The original point...
I saw someone post this solution on Discord: https://discord.com/channels/457912077277855764/689494103380983930/961637486168244294 We might be able to update `svelte-add` to work this way.
> Shouldn't adding `sass` to package.json and leaving `sveltePreprocess()` unconfigured work as well? A user who wants to manually set things up can do this about that easily, yeah! `svelte-add`,...
> This error could be made more understandable by detecting if the adder is based on Preset. If the adder is based on Preset, a friendly error message explaining the...
My intention if I ever get around to this is integrating it as an option to `svelte-add/tailwindcss`, by the way
There is now Tailwind JIT support in [`svelte-add/tailwindcss`](https://github.com/svelte-add/tailwindcss) which is close, right?
Gonna leave this open since WindiCSS has other features Tailwind JIT doesn't.