Update postcss and tailwind #480
Open
+306
−326
Conversation
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
FranjoMindek
approved these changes
Aug 6, 2025
There was a problem hiding this comment.
Works okay.
Now for development version of open-saas, Tailwind CSS will only work with wasp-cli (not wasp) while we don't publish a new Wasp version.
@vincanger For your information.
|
@FranjoMindek should we just wait to merge this until the next Wasp update then? |
|
I would say wait, since we want to be able to develop the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update Tailwind and PostCSS config according to
gitis detecting the Tailwind file as a whole new one because I applied the configuration in the repo's.prettiercand the spacing changes were too big for git to match the files.