Fix conflict with tailwindcss when using @tailwind before @import - #449
Closed
mahdiboomeri wants to merge 1 commit into
Closed
Fix conflict with tailwindcss when using @tailwind before @import#449mahdiboomeri wants to merge 1 commit into
mahdiboomeri wants to merge 1 commit into
Conversation
Collaborator
|
Sorry, we can't be adding support for non-standard at-rules; if we start here, there will be no end to the list. Instead, I suggest you create a file @import "./tailwind-base.css";
@import "./tailwind-components.css";
@import "./buttons.css"; |
Author
|
OK i understand |
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
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.
Hello there
This PR will fix the conflict between postcss-import and tailwindcss when we try to use import after tailwind's @tailwind base or @tailwind components
well obviously we can put @import before these two statements but in the result our custom CSS will be added "before" normalize styles and that is not pretty or standard.
After this PR the above syntax is valid
Sorry for my bad English.