You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know the title sounds vague, but it's true. Using a color/bg class doesn't work in smelte, even the sample documentation at https://smeltejs.com/color for color doesn't work, where they suggest using a class like so:
<divclass="bg-deep-purple-500 text-white p-4">This div is deep purple.</div>
And the corresponding live example fails to show a purple background, right there in any browser. Something must be wrong in the compilation stage.
In order to test this was smelte and not tailwind, I created a new project using tailwind and had colors working in minutes.
My first thought was something to do with pruning, but I'm using development (no pruning). If I add custom colors to rollup.config.js, the appear as css variables, but aren't shown in the relevant .bg-* and .color-* classes.
Since this same issue is happening in the smelte documentation examples, I doubt it's just me.
Oh, and the documentation reads:
Which immediately made me thought I could override tailwind.config.js in some way - but this doesn't appear possible either.
Gutting smelte from this same project and just using tailwind works.
The text was updated successfully, but these errors were encountered:
I know the title sounds vague, but it's true. Using a color/bg class doesn't work in smelte, even the sample documentation at https://smeltejs.com/color for color doesn't work, where they suggest using a class like so:
And the corresponding live example fails to show a purple background, right there in any browser. Something must be wrong in the compilation stage.
In order to test this was smelte and not tailwind, I created a new project using tailwind and had colors working in minutes.
My first thought was something to do with pruning, but I'm using development (no pruning). If I add custom colors to
rollup.config.js
, the appear as css variables, but aren't shown in the relevant.bg-*
and.color-*
classes.Since this same issue is happening in the smelte documentation examples, I doubt it's just me.
Oh, and the documentation reads:
Which immediately made me thought I could override tailwind.config.js in some way - but this doesn't appear possible either.
Gutting smelte from this same project and just using tailwind works.
The text was updated successfully, but these errors were encountered: