New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tailwind Warning in bug signal challenge #857
Comments
Ok, I don't have any warnings 😅 |
Well, have to wait and see if anyone else has these problems and comments here. Do you have the vscode eslint extension installed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since you didn't actually use any Tailwind styling, when you run the app, you get a warning in the terminal. It can be fixed by commenting out the Tailwind styles or removing them. If you want to delete the Tailwind styles, the Tailwind config can be removed as well. Of course, a style could added to the form and then the warning will be gone as well.
Unrelated issue with Tailwind in VSCode, there will be warnings when using
@tailwind
syntax (only seen when user goes to the file).In the VSCode
settings.json
, this could be added to eliminate those warnings:This is really minor stuff, but less confusion for challengers.
The text was updated successfully, but these errors were encountered: