Use PostCSS directly and include Tailwind UI #107
Merged
Conversation
This file contains 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
…anchor-pointing-cursor [bugfix] Anchor is not having pointer cursor on verification resend link
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.
Hey, thanks for creating the preset. I'd like to propose some changes in how Tailwind is referenced.
Following Adam's Tailwind CSS Best Practice Patterns I found quite interesting the use of
postcss-importandpostcss-nested. I think they might be useful as a default. Doing so I removedlaravel-mix-tailwindand added the plugins directly to the Laravel MixpostCssmethod call.I also included
tailwindcss/uias a default instead oftailwindcss/custom-formsto let everyone use the new defaults they introduced.Let me know if these changes make sense for the preset.