> we should support `parseJSON(42)`, `parseJSON(null)`; and all the other wackiness that `JSON.parse` supports

But not pave over the too-lax native implementations of IE8+ and Safari 5.1 Windows? I commented out the below tests because fixing them just didn't seem worth the size.