Need advice about which tool to choose?Ask the StackShare community!
scss-lint vs Stylelint: What are the differences?
scss-lint: Configurable tool for writing clean and consistent SCSS. It is a tool to help keep your SCSS files clean and readable by running it against a collection of configurable linter rules. You can run it manually from the command line, or integrate it into your SCM hooks; Stylelint: A mighty, modern CSS linter. A mighty, modern CSS linter that helps you enforce consistent conventions and avoid errors in your stylesheets.
scss-lint and Stylelint can be categorized as "Code Review" tools.
scss-lint and Stylelint are both open source tools. Stylelint with 6.85K GitHub stars and 628 forks on GitHub appears to be more popular than scss-lint with 3.36K GitHub stars and 508 GitHub forks.
Talkable, 2PAx, and AgFlow are some of the popular companies that use Stylelint, whereas scss-lint is used by Brigade, ikusei, and Doable. Stylelint has a broader approval, being mentioned in 32 company stacks & 36 developers stacks; compared to scss-lint, which is listed in 6 company stacks and 5 developer stacks.
Scenario: I want to integrate Prettier in our code base which is currently using ESLint (for .js and .scss both). The project is using gulp.
It doesn't feel quite right to me to use ESLint, I wonder if it would be better to use Stylelint or Sass Lint instead.
I completed integrating ESLint + Prettier, Planning to do the same with [ Stylelint || Sasslint || EsLint] + Prettier.
And have gulp 'fix' on file save (Watcher).
Any recommendation is appreciated.
In the case of .js files I would recommend using both Eslint and Prettier.
You can set up Prettier as an Eslint rule using the following plugin:
https://github.com/prettier/eslint-plugin-prettier
And in order to avoid conflicts between Prettier and Eslint, you can use this config:
https://github.com/prettier/eslint-config-prettier
Which turns off all Eslint rules that are unnecessary or might conflict with Prettier.
you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.
while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.
prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.
i encourage you to think about what problem you're trying to solve and configure accordingly.
for my teams i set it up like this: - eslint, stylelint, prettier locally installed for cli use and ide support - eslint config prettier (code formatting rules are not eslints business, so dont warn me about it) - vscode workspace config: format on save - separate npm scripts for linting, and formatting - precommit hooks (husky)
so you can easily integrate with gulp. its just js after all ;)
Pura vida! Well, I had a similar issue and at the end I decided to use Stylelint + Prettier for that job, in our case, we wanted that our linting process includes the SCSS files and not only the JS file, base on that we concluded that using only ESLint to do both things wasn't the best option, so, we integrated prettier with Stylelint, and for that we used a neat plugin that allowed us to use Prettier inside Stylelint here is the link, https://github.com/prettier/stylelint-prettier#recommended-configuration, I hope that this can help you, hasta pronto!, :)
Pros of scss-lint
Pros of Stylelint
- Great way to lint your CSS or SCSS5
- Only complains about real problems1
