Replies: 3 comments
-
You have it right, that's the recommended way to do it 👍 You have to tell Tailwind about any folders it needs to scan for classes. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@getJv Yes! that's a right way to release a package that uses tailwind. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the fast answer @adamwathan and @Vijaykv5, this confirmation helped me a lot. Im going to add this step to the lib docs. Great week for you guys. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey Hello.
I published a package let's call it pkg-a. So I installed it into a fresh project ( proj-a ) with tailwind ready to use.
BUT besides proj-a already uses tailwind it does not render the styles used by pkg-a.
Checking the documents I learned if we map the package into the
content key
of tailwind.config.js it will work. and it does:But even if this solves the problem, it does not seem right... if I recommend it to everyone and then install my tailwind packages they will end with several entries in their
content array
So, what are the best practices for releasing packages that use tailwind?
Beta Was this translation helpful? Give feedback.
All reactions