Fix/tailwind v 4 documentation - #71
Merged
mabdullahsari merged 2 commits intoNov 28, 2025
Merged
Conversation
Closed
Collaborator
|
Thank you very much! 🫶 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: Docs: Improve Tailwind CSS v4+ styling instructions to prevent un-styled toasts
This pull request updates the documentation in
README.mdto properly guide users leveraging Tailwind CSS 4+.Problem
The existing instructions are tailored for older Tailwind versions. Following them in v4+ causes Tailwind to fail to discover the package's utility classes. This leaves users with un-styled, potentially transparent notifications, which leads to the false impression that the package is broken or incorrectly configured, in turn generating unnecessary support issues.
Solution
The updated guide now includes the correct
@sourcedirective andcontentarray path for modern Tailwind projects, ensuring the default minimal styling is correctly applied. The instructions for older versions remain untouched.