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
"Circular dependency detected" error on using @apply in custom class #6386
Comments
Same here. |
I upgraded to v3.0.7 in my project with the circular dependency and the error doesn't come up again. Seems like the issue was fixed in #6588. Closing this issue as resolved, thanks @RobinMalfait! 🙏 |
@dcastil Ah perfect! Thanks for notifying and closing the issue! |
I'm still seeing this issue in 3.0.7.
https://play.tailwindcss.com/YxcQz4gSop?file=css In our web components, we have a class If we rename our class to |
I can open a new issue if you want. |
This PR fixed false positives, but the example you posted is not a false positive but an actual circular dependency. It's like you would do this: .btn {
@apply btn;
} |
Ok thanks. I'll update our classes. 👍 |
What version of Tailwind CSS are you using?
v3.0.1
What build tool (or framework if it abstracts the build tool) are you using?
Tailwind Playground
What version of Node.js are you using?
Not applicable
What browser are you using?
Chrome Version 96.0.4664.55
What operating system are you using?
macOS 12.0.1
Reproduction URL
https://play.tailwindcss.com/oslkj6dpmz?file=css
Only change was adding this CSS
Describe your issue
I'm getting a compilation error "<css input>: Circular dependency detected when using:
@apply sr-only
". But I'd expect the project to run without issues. This class was used in Tailwind CSS v2 without any issues.I also don't understand how the circular dependency could come up since I'm using a class name not available in Tailwind CSS:
group-inner-focus-within:sr-only
. The issue goes away when I remove the last charactery
from the class. Seems like Tailwind tries to evaluate the class as a Tailwind class despite the prefix not existing in Tailwind.The text was updated successfully, but these errors were encountered: