Open ronilaukkarinen opened 3 years ago
Oh, never mind, that plugin supports SCSS out of the box... closing this.
Got it running on my editor, yes, but let's say I want doiuse to be part of our travis workflow. What command do I use to enable SCSS support in doiuse
?
it's reporting
You tried to parse SCSS with the standard CSS parser; try again with the postcss-scss parser
I installed said postcss-scss parser, but doiuse won't utilize it. Is there some config option? It' sad we can't lint .scss files :(
I'd be very interested in this as well!
It's not exactly a core feature I think we should support, since we'd be overcomplicating the scope of the project by drawing in more dependencies.
Generally, you'd use postcss
with a preprocessor either at the command line level before piping or with stylelint (which also uses postcss
). Personally, I don't use the cli much because I have the errors built into the IDE.
That said, we should probably have a guide somewhere at minimum. Next, we should be probably add some tests to ensure you can pipe SCSS over.
I'd like to lint .scss files.
Produces:
I never work with outputted CSS files. It would be amazing to be able to use vscode plugin and see the browser support directly on editor linter OR even implement this to a gulp task.