Fix for #1770 with Tailwind #2475
Open
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
such as when running in the background in a non-interactive shell (such as in docker). See tailwindlabs/tailwindcss#9966 for details.
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 Text component changes are unrelated to #1770 however as I was testing with the tailwindcss branch the errors prevented me from using pages. src/pages/UserAccountPage.js had the Text component added in the migration from headings to Text, so the rest looked like a miss with assuming Text was already imported.
Concern: public/css/stylesheet.css is being committed while also built via tailwindcss might result in confusion, whether to edit src/css/stylesheet.css or public/css/stylesheet.css