When comparing Pretty JSON vs JSHint, the Slant community recommends Pretty JSON for most people. In the question“What are the best plugins for Sublime Text?” Pretty JSON is ranked 20th while JSHint is ranked 35th. The most important reason people chose Pretty JSON is:
To prettify look for "Pretty JSON: Format (Pretty Print) JSON" via Command Pallette. Indent, key sorting and ASCII ensurance can all be configured.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Can prettify with configurable indent and optional key sorting
To prettify look for "Pretty JSON: Format (Pretty Print) JSON" via Command Pallette. Indent, key sorting and ASCII ensurance can all be configured.
Pro Can convert JSON to XML
To convert JSON to XML look for "Pretty JSON: JSON 2 XML" via Command Pallette.
Pro Can minify
To compress/minify look for "Pretty JSON: Minify (compress) JSON" via Command Pallette.
Pro Can query
Query/filter requires ./jq and allows slicing, filtering, mapping and transforming data with ease. To query look for "Pretty JSON: jq query" via Command Pallette.
Pro Customizable ruleset
Since it's creation, JSHint was created to be a more configurable version of JSLint (it's actually a fork of JSLint itself). Every rule is configurable through a configuration file.
Pro Comes with support for many librariers
JSHint supports libraries like QUnit, NodeJS, jQuery, Mocha out of the box.
Pro Basic ES6 support
Basic ES6 support is included.
Cons
Con No way to support ESnext
There's no support for ESnext available.
Con Difficult to know which rule is causing an error
Because it does not display the rule name that is being broken, it's difficult to know which rule is actually causing the error.