Centralizing Tailwind config across teams/repos #5528
gplusdotgr
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are considering adopting tailwindCSS to our organization, and I was wondering how we would be able to have one centralized tailwind configuration shared across several repositories (we use VueJS/NuxtJS). The configuration would define our brand colors, breakpoints, spacings and more.
What is challenging for us is how to have only 1 dist CSS file compiled - cached and shared across pages. (we use micro-frontends). Sharing a configuration is easy but that would mean every app would have to re-build and re-compile tailwind separately.
I guess with JIT compiler we have to compile Tailwind for every app separately, but maybe I'm wrong?
Would maybe in our case having a pre-compiled tailwind custom distribution file be ultimately faster rather than using the JIT compiler?
Beta Was this translation helpful? Give feedback.
All reactions