This repository was archived by the owner on Jan 3, 2023. It is now read-only.
Make warnings non-fatal - #3
Open
m1cr0man wants to merge 1 commit into
Open
Conversation
esbuild will still produce valid CSS even if warnings are encountered. Instead of hard-failing the build just inform the user and carry on.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
esbuild will still produce valid CSS even if warnings are encountered. Instead of hard-failing the build just inform the user and carry on.
Currently trying to use @tailwindcss/typography produces warnings due to the use of a case-sensitive modifier on an attribute selector, which esbuild's css interpreter complains about.