https://srveditorial-st11.itunes.apple.com/WebObjects/SRVEditorial.woa/wa/debug?store=sundance-root&key=SF6_132006_143503

.gitignore

@@ -1,4 +1,4 @@
-compass_app_log.txt
-/dist/
+/.idea/
+/build/
+/release/
 /node_modules/
-/.sass-cache/

LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2017 Nik Rolls, Callum Lock
+
+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.

README.md

@@ -1,16 +1,17 @@
 JSON Formatter
 ==============
 
-Chrome extension for printing JSON and JSONP nicely when you visit it 'directly' in a browser tab.
+Browser extension for printing JSON and JSONP nicely when you visit it 'directly' in a browser tab.
 
 Features
 --------
 
 * JSONP support
 * Fast, even on long pages
 * Works on any valid JSON page – URL doesn't matter
-* Syntax highlighting
+* Syntax highlighting with 36 light and dark themes
 * Collapsible trees, with indent guides
+* Line numbers
 * Clickable URLs
 * Buttons for switching between raw and parsed JSON
 * Parsed JSON is exported as a global variable, `json`, so you can inspect it in the console
@@ -20,39 +21,30 @@ A background worker is used to prevent the UI freezing when processing very long
 Installation
 ------------
 
-**Option 1** – just install it from the [Chrome Web Store](https://chrome.google.com/webstore/detail/bcjindcccaagfpapjjmafapmmgkkhgoa).
+**Option 1** – Install it from the [Chrome Web Store](https://chrome.google.com/webstore/detail/mhimpmpmffogbmmkmajibklelopddmjf/) or [Windows Store](https://www.microsoft.com/en-us/store/p/json-formatter-for-edge/9nz9d2j86w6s).
 
-**Option 2** – install it from source:
+**Option 2** – 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.
+1. Clone/download this repo
+2. Install dependencies using [NPM](https://nodejs.org/) or [Yarn](https://yarnpkg.com/en/).
+3. Build the extension: `gulp build:dist`
+4. Side-load the extension in your browser as per below
 
-**Some URLs to try it on:**
-
-* http://feeds.delicious.com/v2/json/popular?callback=hello
-* http://gdata.youtube.com/feeds/api/standardfeeds/most_popular?alt=json&v=2
-* http://twitter.com/statuses/public_timeline.json
-
-FAQ
----
-
-### Why are large numbers not displayed accurately?
+Chrome
 
-This is a [limitation of JavaScript](http://www.ecma-international.org/ecma-262/5.1/#sec-15.7.3.2) (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.
+5. Open Chrome and go to `chrome://chrome/extensions/`
+6. Enable "Developer mode"
+7. Click "Load unpacked extension"
+8. Select the `build` folder created in step 3
 
-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.
+Edge
 
-If you want to use long sequences of digits in your JSON, then **quote them as strings**.
+5. Open Edge and go to `about:flags`
+6. Enable the option "Enable extension developer features" and restart the browser
+7. Click on the ellipsis (...) menu, click "Extensions", and click "Load extension"
+8. Select the `build` folder created in step 3
 
-### 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](http://www.ecma-international.org/ecma-262/5.1/#sec-12.6.4). 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](https://code.google.com/p/v8/issues/detail?id=164) – 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
+**Some URLs to try it on:**
 
-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.
+* https://en.wikipedia.org/w/api.php?action=query&titles=Main%20Page&prop=contributors&format=json
+* http://api.flickr.com/services/feeds/photos_public.gne?jsoncallback=jsonp&tags=json&tagmode=any&format=json