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
{{ message }}
This repository has been archived by the owner on Jun 22, 2024. It is now read-only.
I noticed that you used dynamic class names in your components. This is problematic because dynamic class names are not recognised by tailwind, and hence, not generated into the output css.
All the hover variables in colors.js are an example of that, but there are more such as focus:{{...}} or sm:{{...}}
Only solution is to have colors.js (and others ofc) reference only the full class names and remove modifiers such as hover:{{...}} or sm:{{...}} etc from source template files.
eg: colors.js
Hi,
I noticed that you used dynamic class names in your components. This is problematic because dynamic class names are not recognised by tailwind, and hence, not generated into the output css.
All the hover variables in
colors.js
are an example of that, but there are more such asfocus:{{...}}
orsm:{{...}}
Only solution is to have
colors.js
(and others ofc) reference only the full class names and remove modifiers such ashover:{{...}}
orsm:{{...}}
etc from source template files.eg:
colors.js
see the tailwind documentation on this https://tailwindcss.com/docs/content-configuration#dynamic-class-names
The text was updated successfully, but these errors were encountered: