Adding Tailwind CSS for Shared UI Components #429
-
|
Hello, That is, avoiding to download multiple tailwindcss dependencies for each The cleanest solution or implementation I've found/tried so far, is the one found in the turborepo-tailwindcss I pushed earlier. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
If the packages are not being published, the best solution is to leverage tailwind JIT in the applications such that there are no interim CSS files produced at all. If the packages are being published, then you will need to generate independent CSS files, or document/state in docs that the package needs to be included in the JIT settings somehow |
Beta Was this translation helpful? Give feedback.
-
|
Thought as much .. If I may ask, do you have an example of how to accomplish the scenario of not publishing the packages ? Or can you describe the process of leveraging the Tailwind JIT in the applications ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I'm also working on something like this. Ended up using tailwind CLI to output a final CSS file eg. Here's the repo I'm working on, hope you find it useful: The main folders you might be interested in are:
|
Beta Was this translation helpful? Give feedback.
-
|
It looks good ! Basically you used the Tailwind CLI to implement the same workaround this repo uses: turborepo-tailwindcss. The solution or workaround is broken down as follows:
The advantage of your solution is that, for |
Beta Was this translation helpful? Give feedback.
If the packages are not being published, the best solution is to leverage tailwind JIT in the applications such that there are no interim CSS files produced at all.
If the packages are being published, then you will need to generate independent CSS files, or document/state in docs that the package needs to be included in the JIT settings somehow