You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2020. It is now read-only.
this doesn't solve the problem as in this case what's being linted is the output of node-sass rather than the source code and so source code can get messy without getting any linting warnings.
I invite you to think about possible solutions and post them here.
For now I've removed stylelint plugin from postcss-loader in my webpack config. Hope to have it fixed properly at some point.
The text was updated successfully, but these errors were encountered:
Isn't it better to lint the sass before it's transformed? I mean, what should be linted is the source code, right?
You can lint sass with sass-lint, to stay in the node ecosystem. I use it in atom, but it shouldn't be hard including it in your webpack pipeline if you want to lint at build time
In continue to #812.
Adding
sass-loader
afterpostcss-loader
inwebpack.config.babel.js
causes stylelint warnings like:That's because libsass transforms outputted CSS according to outputStyle option which can take one of 4 values:
nested
(default)expanded
compact
compressed
While these warnings can be prevented by setting
outputStyle
toexpanded
inwebpack.config.babel.js
:this doesn't solve the problem as in this case what's being linted is the output of
node-sass
rather than the source code and so source code can get messy without getting any linting warnings.I invite you to think about possible solutions and post them here.
For now I've removed
stylelint
plugin from postcss-loader in my webpack config. Hope to have it fixed properly at some point.The text was updated successfully, but these errors were encountered: