prettier VS JSHint

Compare prettier vs JSHint and see what are their differences.

JSHint

JSHint is a tool that helps to detect errors and potential problems in your JavaScript code (by jshint)
Our great sponsors
  • Scout APM - A developer's best friend. Try free for 14-days
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • SaaSHub - Software Alternatives and Reviews
prettier JSHint
138 6
41,318 8,656
1.1% 0.2%
9.9 5.5
4 days ago 25 days ago
JavaScript JavaScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

prettier

Posts with mentions or reviews of prettier. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-06.

JSHint

Posts with mentions or reviews of JSHint. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-22.
  • NPM package ‘ua-parser-JS’ with more than 7M weekly download is compromised
    13 projects | news.ycombinator.com | 22 Oct 2021
    > check out the Web X-Ray repo <https://github.com/mozilla/goggles.mozilla.org/>.

    Thanks for example. Peeking a bit under the hood, it appears to be due to transitive dependencies referencing github urls (and transient ones at that) instead of semver, which admittedly is neither standard nor good practice...

    FWIW, simply removing `"grunt-contrib-jshint": "~0.4.3",` from package.json and related jshint-related code from Gruntfile was sufficient to get `npm install` to complete successfully. The debugging just took me a few minutes grepping package-lock.json for the 404 URL in question (https://github.com/ariya/esprima/tarball/master) and tracing that back to a top-level dependency via recursively grepping for dependent packages. I imagine that upgrading relevant dependencies might also do the trick, seeing as jshint no longer depends on esprima[0].

    I'm not sure how representative this particular case is to the sort of issues you run into, but I'll tell that reproducibility issues can get a lot worse in ways that committing deps doesn't help (for example, issues like this one[1] are nasty to narrow down).

    But assuming that installation in your link just happens to have a simple fix and that others are not as forgiving, how is committing node_modules supposed to help here if you're saying you can't even get it to a working state in the first place? DO you own the repo in order to be able to make the change? Or are you mostly just saying that hindsight is 20-20?

    [0] https://github.com/jshint/jshint/blob/master/package.json#L4...

    [1] https://github.com/node-ffi-napi/node-ffi-napi/issues/143

  • Cyclomatic complexity: Why QAs (and Devs) should worry about it
    1 project | dev.to | 17 Oct 2021
    And another 50 warnings, measured in JSHint. Some words were removed and/or modified to not identify the product and translated to English.
  • Javascript Security Checklist
    5 projects | dev.to | 29 Sep 2021
    JSHint.
  • Script-loading script fails on a particular script
    1 project | reddit.com/r/learnjavascript | 17 Aug 2021
    As expected, that code is never executed (neither memsq nor cachedsq exist), so as you point out, the script is not being loaded. I ran both scripts through JSHint, but only got warnings about using the ES6 flag in the site (which I don't know how to do); no errors. The unloaded script works quite well on Node, and when pasting it directly into the console, as I already mentioned, so this script has no errors that prevents it from running. :/
  • Design an Effective Build Stage for Continuous Integration
    12 projects | dev.to | 8 Apr 2021
    As you can imagine, the language changed a lot over time, and not all its parts are good. Using a linter will help us stay away from the bad parts of JavaScript. In my experience, the ESlint and JSHint linters integrate very well into the CI environment. Any of these can be installed with npm install --save-dev.
  • JavaScript Course — Part 3/
    1 project | dev.to | 11 Feb 2021

What are some alternatives?

When comparing prettier and JSHint you can also consider the following projects:

JS-Beautifier - Beautifier for javascript

black - The uncompromising Python code formatter

ESLint - Find and fix problems in your JavaScript code.

Standard - 🌟 JavaScript Style Guide, with linter & automatic code fixer

Drawflow - Simple flow library 🖥️🖱️

husky - Git hooks made easy 🐶 woof!

clojure-style-guide - A community coding style guide for the Clojure programming language

Tailwind CSS - A utility-first CSS framework for rapid UI development.

PostCSS - Transforming styles with JS plugins

prettier-plugin-organize-imports - Make Prettier organize your imports using the TypeScript language service API.

jscs