Need advice about which tool to choose?Ask the StackShare community!
Codebrag vs Stylelint: What are the differences?
Developers describe Codebrag as "Have fun while doing code reviews". Codebrag saves you time with well‑organized and enjoyable code reviews. A simple dashboard combined with a game‑like experience brings fun to the process and makes it work for your team. Codebrag gamifies the experience with achievements, leader boards, gravatars and 'Likes' for the code. Codebrag is built by developers with over 10 years experience in programming, working on projects all over the world. It is developed with passion answering a real need to make code reviews an easier and more pleasant experience. On the other hand, Stylelint is detailed as "A mighty, modern CSS linter". A mighty, modern CSS linter that helps you enforce consistent conventions and avoid errors in your stylesheets.
Codebrag and Stylelint can be primarily classified as "Code Review" tools.
Stylelint is an open source tool with 6.76K GitHub stars and 615 GitHub forks. Here's a link to Stylelint's open source repository on GitHub.
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 Codebrag
- Simple, SVN support, easy install and free1
Pros of Stylelint
- Great way to lint your CSS or SCSS5
- Only complains about real problems1
