Add VisualJSON v1.6.0
=====================
<!-- If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so. -->
After making all changes to the cask:
- [x] `brew cask audit --download {{cask_file}}` is error-free.
- [x] `brew cask style --fix {{cask_file}}` reports no offenses.
- [x] The commit message includes the cask’s name and version.
Additionally, if **adding a new cask**:
- [x] Named the cask according to the [token reference].
- [x] `brew cask install {{cask_file}}` worked successfully.
- [x] `brew cask uninstall {{cask_file}}` worked successfully.
- [x] Checked there are no [open pull requests] for the same cask.
- [x] Checked the cask was not already refused in [closed issues].
- [x] Checked the cask is submitted to [the correct repo].
[token reference]: https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/token_reference.md
[open pull requests]: https://github.com/caskroom/homebrew-cask/pulls
[closed issues]: https://github.com/caskroom/homebrew-cask/issues?q=is%3Aissue+is%3Aclosed
[the correct repo]: https://github.com/caskroom/homebrew-cask/blob/master/doc/development/adding_a_cask.md#finding-a-home-for-your-cask
[version-checksum]: https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/sha256.md#updating-the-sha256
---
A JSON visualizer with tree view.
emscripten: fix for python3
===========================
- [x] Have you followed the [guidelines for contributing](https://github.com/Homebrew/homebrew-core/blob/master/CONTRIBUTING.md)?
- [x] Have you checked that there aren't other open [pull requests](https://github.com/Homebrew/homebrew-core/pulls) for the same formula update/change?
- [x] Have you built your formula locally with `brew install --build-from-source <formula>`, where `<formula>` is the name of the formula you're submitting?
- [x] Does your build pass `brew audit --strict <formula>` (after doing `brew install <formula>`)?
-----
When `/usr/bin/env python` resolves to `python 3.x`, wrapper scripts like `emcc` uses a different loading strategy than python 2.x: they directly call underlying scripts like `emcc.py` from the same directory. Unfortunately, currently they do not resolve symlinks when calculating the directory, so our `#{HOMEBREW_PREFIX}/bin/emcc` symlink can't load `#{libexec}/emcc.py`. This is being addressed in https://github.com/kripken/emscripten/pull/5534.
The test is updated to a much more useful one.
I'm using formula-patches since the PR patch does apply cleanly to the stable tarball.
Also, I don't think this deserves a revision bump, since people seem to be happily using Python 2.7 so far. Guess I'm the first weirdo who both use Python 3.x as default and decided to install this.
Resolve symlinks in em* wrapper scripts
=======================================
When wrapper scripts `em*` in `PATH` are symlinks to the actual scripts installed alongside `em*.py` (e.g. in the case of a Homebrew installation), we need to resolve symlinks in order to find `em*.py`.