DJSON Viewer and Formatter

Chrome extension for printing and formatting JSON and JSONP nicely directly in a browser tab. Initial base of the formatter from: callumlocke json-formatter. Using developer utils from: hasher

Features

• Format JSON and JSONP input or responses
• Minify or Beautify JSON
• Theme support
• Syntax highlighting
• Collapsible trees, with indent guides
• Recursive collapsible elements
• Clickable URLs
• Toggle between raw and parsed JSON
• Line numbers
• Works on any valid JSON page – URL doesn't matter
• Works on local files too (if you enable this in chrome://extensions)
• You can inspect the JSON by typing djson in the console
• Counts items and properties in a collection
• Show JSON path of the elements on hover and copy it with the context menu
• Option to start with JSON collapsed (always or if the file is big)
• Recognize nested JSON strings in properties value
• Hashes, Encode, Time Strings, Numbers utils

A background worker is used to prevent the UI freezing when processing very long JSON pages.

Installation

Option 1 – Install through Chrome Web Store

Option 2 – install it using the packed version:

• clone/download this repo or just download the file djson-viewer.crx,
• open Chrome and go to chrome://chrome/extensions/,
• drag the djson-viewer.crx into Chrome
• accept to install the extension

Option 3 – install it from source:

• clone/download this repo,
• open Chrome and go to chrome://chrome/extensions/,
• enable "Developer mode",
• click "Load unpacked extension",
• select the extension folder in this repo.

Pro Tip

• Hold down control (or cmd on Mac) while collapsing a tree if you want to collapse all its siblings too.
• Hold down shift while collapsing a tree if you want to collapse also all his children

FAQ

Why are large numbers not displayed accurately?

This is a limitation of JavaScript (and therefore JSON). The largest possible number is Number.MAX_SAFE_INTEGER, or 9007199254740991. If you try to use a number larger than this in JavaScript/JSON, you'll lose accuracy.

The idea of JSON Formatter is to show you how the computer sees your JSON, so we don't attempt to circumvent this limitation, otherwise that would give a misleading representation of your data. It's better to see exactly what V8 sees.

If you want to use long sequences of digits in your JSON, then quote them as strings.

Why are object keys sometimes in the wrong order?

What you see in JSON Formatter is a representation of the parsed object/array. You see what V8 sees.

Plain JavaScript objects are unordered collections of properties. If you go through them with for...in, for example, there is no guarantee of any particular order. In practice, most engines maintain the order in which the keys were first declared, but V8 moves any numeric keys (e.g. "1234") to the front, for a small performance gain. This was a controversial issue – a lot of people think it sucks that you can't predict key enumeration order in Chrome – but the V8 team refused to 'fix' it, because it's not a bug, and they're right. If you want your values to be in a certain order, and you're relying on the non-standard key-ordering logic of a particular engine, then your code is broken. Restructure your data to use arrays.

But I just want it to be in order for readability

That would require manually parsing the JSON string with regular expressions (instead of using JSON.parse), which would be too slow. And it's not a good idea to go down the road of representing the data differently from how the engine actually sees it.

LICENCE

DJSON Viewer and Formatter | MIT License Copyright 2017 Dario De Santis

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.