Need advice about which tool to choose?Ask the StackShare community!

Hound

42
46
+ 1
14
Sass Lint

27
43
+ 1
0
Add tool

Hound vs Sass Lint : What are the differences?

What is Hound? A hosted service that comments on Ruby style guide violations in your GitHub pull requests. Take care of pesky code reviews with a trusty Hound. Hound reviews GitHub pull requests for style guide violations.

What is Sass Lint ? Pure Node.js Sass linting. It is a Node-only Sass linter for both sass and scss syntax. It can be run through a command line interface. Special comments can be used to disable and enable certain rules throughout your source files in a variety of scenarios.

Hound and Sass Lint can be primarily classified as "Code Review" tools.

Hound and Sass Lint are both open source tools. It seems that Hound with 1.73K GitHub stars and 395 forks on GitHub has more adoption than Sass Lint with 1.7K GitHub stars and 550 GitHub forks.

thoughtbot, Punchh, and Verba are some of the popular companies that use Hound, whereas Sass Lint is used by WeAreHive, Stickler CI, and Litural. Hound has a broader approval, being mentioned in 12 company stacks & 15 developers stacks; compared to Sass Lint , which is listed in 3 company stacks and 5 developer stacks.

Advice on Hound and Sass Lint
Needs advice
on
ESLintESLintSass Lint Sass Lint
and
StylelintStylelint

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.

See more
Replies (3)
Amaro Mariño
Senior Frontend Developer at Landbot.io · | 6 upvotes · 151K views
Recommends
on
ESLintESLint

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.

See more
Alexis Villegas Torres
Software Engineer at SpeedUrWeb · | 5 upvotes · 150.7K views
Recommends
on
StylelintStylelint

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!, :)

See more
Alex Spieslechner

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 ;)

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Hound
Pros of Sass Lint
  • 4
    Comments on style so I don't have to
  • 3
    Easy configuration
  • 3
    Fast
  • 2
    Free for OSS
  • 2
    Inline comments
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    - No public GitHub repository available -

    What is Hound?

    Automated code review for GitHub pull requests. It comments on code quality and style issues, allowing you and your team to better review and maintain a clean codebase.

    What is Sass Lint ?

    It is a Node-only Sass linter for both sass and scss syntax. It can be run through a command line interface. Special comments can be used to disable and enable certain rules throughout your source files in a variety of scenarios.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Hound?
    What companies use Sass Lint ?
    See which teams inside your own company are using Hound or Sass Lint .
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Hound?
    What tools integrate with Sass Lint ?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Hound and Sass Lint ?
    ESLint
    A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
    Prettier
    Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
    TSLint
    An extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. It is widely supported across modern editors & build systems and can be customized with your own lint rules, configurations, and formatters.
    SonarQube
    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
    Stylelint
    A mighty, modern CSS linter that helps you enforce consistent conventions and avoid errors in your stylesheets.
    See all alternatives