fix: Use css-tree instead of css for parsing /colors#1211
Merged
Conversation
047995c to
24ab854
Compare
/colors
/colorscss-tree instead of css for parsing /colors
24ab854 to
c5300df
Compare
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.
the npm package
csshas a depreciated dependency that's generating a warning onnpm install, switching tocss-treeresolves the issue as a drop in replacement.Also introduced a
tbodyelement on the colors page to silence this warning:Reproducing
First, on
main:rm -r node_modules && npm iObserve depreciation warning.
Then, on this branch:
rm -r node_modules && npm iWarning should be gone.