Need advice about which tool to choose?Ask the StackShare community!
Sass Lint vs Stylelint: What are the differences?
1. Configuration and Rules: Sass Lint allows configuration through a
.sass-lint.ymlfile, where specific rules can be defined for the linter. Stylelint, on the other hand, uses astylelint.config.jsJavaScript file for configuration. Both tools have a wide range of rules available, but Sass Lint focuses more on Sass-specific rules while Stylelint provides more general CSS rules.2. Language Support: Sass Lint is primarily designed to support SCSS and Sass syntax, offering specific rules for these languages. Stylelint, on the other hand, covers a broader range of CSS syntax, including SCSS, Less, and CSS-in-JS.
3. Integration and Usage: Sass Lint can be integrated with other tools through various plugins and CLI integrations. It can be used from the command line to lint individual files or entire directories. Stylelint, on the other hand, can be used as a standalone CLI tool, integrated into build processes, or even used in text editors through plugins.
4. Error Reporting: Sass Lint provides detailed error reports with line numbers and descriptions for each issue found. Stylelint also provides thorough error reporting, but it offers additional features like auto-fixing certain issues and support for custom formatters.
5. Compatibility: Sass Lint is specifically built for Sass and SCSS syntax, making it less compatible with other CSS languages. Stylelint, on the other hand, supports multiple CSS syntaxes, making it more versatile for projects using different CSS languages.
6. Community and Support: Sass Lint has an active community and a dedicated team maintaining the project. It has been around for a longer time and has a mature ecosystem of plugins and integrations. Stylelint also has a strong community involvement and active development, with a growing set of plugins and integrations.
In Summary, Sass Lint and Stylelint differ in their configuration and rules, language support, integration and usage, error reporting, compatibility, and community and support.
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.
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!, :)
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 ;)
Pros of Sass Lint
Pros of Stylelint
- Great way to lint your CSS or SCSS5
- Only complains about real problems1
