-
Notifications
You must be signed in to change notification settings - Fork 180
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
Unexpected unknown at-rule "@screen" at-rule-no-unknown #263
Comments
Can you try to upgrade to Tailwind 2? |
Even on 2.15 it's not Tailwind 2 by default? |
Not yet. |
Just followed this: https://tailwindcss.nuxtjs.org/setup#tailwind-2
Still have this issue: Is this a bug? |
This is also not working on the latest version 4.0.1 with tailwind 2. |
As a workaround, it's possible to bypass this error from stylelint
rules: {
'at-rule-no-unknown': [
true,
{
ignoreAtRules: ['extends', 'tailwind', 'screen'],
},
],
},
|
@Atinux can you look at this? It seems like this module works only with |
Please create a reproduction on CodeSandBox by forking https://codesandbox.io/s/nuxt-tailwindcss-o4vn5pvp7q?from-embed |
builds are failing: https://codesandbox.io/s/pedantic-heisenberg-zommu?file=/pages/index.vue |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The issue still there for me with tailwind 3.3.0 |
I am still experiencing the same issue. |
Hi, sorry - I believe this to be a postcss thing that Tailwind. I'm not aware of a Please feel free to correct me if I'm wrong. |
Oh yes very strange, I found this documentation but is it from v0 😄 https://tailwindcss-v0.netlify.app/docs/functions-and-directives/#screen |
@sovetski It's here to stay.. tailwindlabs/tailwindcss#7516 |
Node v14
Whenever i try to use any tailwind directive except
@apply
it throws me an error: "Unexpected unknown at-rule "@screen" at-rule-no-unknown", nor screen, nor layer works.Example code:
tailwind.config.js:
@Atinux might be related to npm?
The text was updated successfully, but these errors were encountered: