LLVM to JS
The escape() method does not encode the + character which is interpreted as a space on the server side as well as generated by forms with spaces in their fields. Due to this shortcoming and the fact that this function fails to handle non-ASCII characters correctly, you should avoid use of escape() whenever possible. The best alternative is usually encodeURIComponent(). escape() will not encode: @*/+ encode URL
The good parts...
Version 8.0 This new major release is quite a big overhaul bringing both new features and some backwards incompatible changes. However, chances are that the majority of users won't be affected by the latter: the basic scenario described in the README is left intact. Here's what did change in an incompatible way: Another technically compatible change that nonetheless might need attention: