Bob
Don't use `@import` inside a style block to import the directives with SvelteKit. Import the directive file into a script block using `.css` as the extension.
You could just setup a new SvelteKit project with tailwind and PostCSS in the setup window. Then install Smelte and import the non-compiled components. That should really be the only...
Ok, so I see your issue. Since SvelteKit doesn't use Rollup, you won't get the theme unless you modify a bit.. I'll create a repo to get it functioning.
Actually, I'll just post the fix here. Change the following in a fresh SvelteKit project with tailwind (JIT or not) and static adapter: - `tailwind.config.js` ```javascript const { tailwindExtractor }...
A permanent fix for this, to make it usable with existing Svelte projects and SvelteKit projects, would be to convert the Rollup plugin to a postcss "plugin". It might be...
No problem! And that's odd, hopefully it's a simple fix.
I hope it has a more solid solution, because that safelist can get insanely large depending on the project... given that programmatic generation in general is pretty standard amongst add-in...
@sjmcdowall Sorry about that, inside the colors object, wrap the custom colors in an extend object, like: ```javascript ... colors: { extend: { ... } } ... ``` This will...
Like I said, hopefully it's ported to a usable plugin for SvelteKit since Rollup isn't available.
I'm not sure how you're setting up two-way binding, but the easiest way to test it would be to use a store that you pass to the component via render,...