`@include` throwing `at-rule-no-unknown`
See original GitHub issueI’m getting the following error when using @include
The configuration .stylelintrc
plugins:
- stylelint-scss
extends:
- stylelint-config-standard
Is this an error or have I configured something wrong? Thanks
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:7
Top Results From Across the Web
`@include` throwing `at-rule-no-unknown` · Issue #196 - GitHub
I'm getting the following error when using @include The configuration .stylelintrc plugins: ... @include throwing at-rule-no-unknown #196.
Read more >stylelint throws at-rule-* errors when parsing LESS variables
(1:1) Unexpected unknown at-rule "@fadeAnimDuration:" (at-rule-no-unknown). It seems that this was once a known issue but should have been ...
Read more >@tailwind unknown at rule | The AI Search Engine You Control
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, ...
Read more >stylelint | Yarn - Package Manager
A mighty, modern linter that helps you avoid errors and enforce conventions in your styles. Features. It's mighty as it: has over 170...
Read more >VS Code Errors and Warnings when using @tailwind directives
I have been using tailwindcss with laravel and laravel mix. I am having kind of weird issue because everything is working fine but...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hmm… I’m not sure which rules
stylelint-config-standard
includes, but you have to use the SCSS version of the rule, so this should help:@gadzhimari Good that you got it fixed.
When I looked at your message, the config looked different so that’s why I replied like that. I guess that you edited it afterwards.