-
Notifications
You must be signed in to change notification settings - Fork 186
Warning "Unrecognized at-rule or error parsing at-rule ‘@tailwind’." in clean install #190
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
Comments
I've found this as well, which caused a lot of confusion. This behavior also prevents you from using For context: The default
Which includes
On build, it just copies the |
I would welcome a PR with an update to the README's "Troubleshooting" section. |
Add a paragraph to the Troubleshooting section about resolving a misconfiguration that otherwise causes double-processing of Tailwind's entry file, as described in issue rails#190.
@flavorjones You think this (#313) would do? |
When starting a new rails 7 app and adding, then installing, tailwindcss-rails, and adding a single route using layout, the resulting page will produce this warning in the browser console:
The
@tailwind
at-rule should obviously not be in the processed output.It still is, because the standard
app/assets/stylesheets/application.css
file contains the= require_tree .
directive. This way, while the tailwind preprocessing does handle everything correctly, in addition theapplication.tailwind.css
file is processed in the asset pipeline. It is concatenated into the fingerprinted application.css verbatim.It does little damage, because all styles are working, but it's confusing and dirty. It might be obvious for many, but the docs for installation could use a note to change a possibly existing default
application.css
manifest.Rails 7.0.3.1
tailwindcss-rails 2.0.12
The text was updated successfully, but these errors were encountered: