Tailwind config when selecting TailWind as styling library during setup #2377
-
Hello, Upon setting up my storefront, i selected TailWind for the styling library. Tailwind is working; i can use all of my basic utility classes just fine, but i'm used to there being a tailwind.config.js in the root where i can extend tailwind to include custom colors. I figured i just needed to run It seems like if you do the automated tailwind set up, you end up with a non-traditional install of tailwing that hinders the abiilty to extend it? I feel like i have to be missing something. I'd hate to start over so i could seletct no styling library during scaffolding and add it in myself after, but i feel like thats the next step here; unless im just missing something altogether. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi 👋 -- The automated Tailwind setup is v4 (alpha), as stated in the init process dialogs. The v4 has a different way to configure things. If you open your You can always downgrade to v3 if you prefer the traditional way. |
Beta Was this translation helpful? Give feedback.
-
I know this was answered but you need to make sure you import the tailwind.css file as well. I missed this! import tailwindStyles from '~/styles/tailwind.css?url'; And then add it to the links method in export function links() {
return [
// ...
{rel: 'stylesheet', href: tailwindStyles},
// ...
];
} |
Beta Was this translation helpful? Give feedback.
Hi 👋 -- The automated Tailwind setup is v4 (alpha), as stated in the init process dialogs. The v4 has a different way to configure things. If you open your
app/styles/tailwind.css
file, you'll see a link to the official docs for this version.You can always downgrade to v3 if you prefer the traditional way.