Fix tailwind css bug#39
Draft
morbargig wants to merge 2 commits into
Draft
Conversation
…ded corners - Replace dark mode colors with white background and light colors - Add gentle gradient fade (from-white via-white/95 to-white/40) for smooth text coverage - Increase border radius to rounded-3xl for more rounded appearance - Simplify all CSS classes to standard Tailwind utilities - Ensure fixed positioning covers content when scrolling (z-50) - Update text colors for white background (text-gray-900 for textarea, text-gray-500 for helper text)
Co-authored-by: morbargig <morbargig@gmail.com>
|
Cursor Agent can help with this pull request. Just |
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.
Fix Tailwind CSS not working by correcting content paths and ensuring proper PostCSS and Vite configuration.
The primary issue was incorrect content paths in
apps/frontend/tailwind.config.cjs, which were specified relative to the project root instead of relative to the config file's location. Additionally, PostCSS and Vite configurations were updated to explicitly resolve the Tailwind config using absolute paths, preventing potential resolution issues.