Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Pretty JSON vs JSLint, the Slant community recommends JSLint for most people. In the question“What are the best plugins for Sublime Text?” JSLint is ranked 18th while Pretty JSON is ranked 20th. The most important reason people chose JSLint is:
Since it's relatively old (it was made in 2002) and made by Douglas Crockford, considered a JavaScript God by many JavaScript programmers. It was created to enforce what in Crockford's experience are the good parts of JavaScript. This means that it's considered by many the best way to enforce the highest standards in JavaScript.
Question 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 Enforces a very high standard
Since it's relatively old (it was made in 2002) and made by Douglas Crockford, considered a JavaScript God by many JavaScript programmers. It was created to enforce what in Crockford's experience are the good parts of JavaScript. This means that it's considered by many the best way to enforce the highest standards in JavaScript.
Pro No setup required
JSLint comes preconfigured and ready to be used.
Cons
Con Highly opinionated
JSLint has a very strict, dogmatic ruleset that cannot be changed or warnings turned off. So much so that rarely any code will pass JSLint tests. It's reasonable to evaluate if all warning are worth changing.
Con Difficult to know which rule is causing which error
Since you can't edit the rules and it's not programmed in a way to display the rule that's being broken, it's difficult to understand which rule has been broken.
Con No way to support ESnext
