fixed error messages of JSON parsing is failed

[ivan-demchenko]

I stumbled upon a nasty behaviour. I had an issue with one of the 100+ schemas is my RAML and it took me a few hours to debug the code and find out that the reason was a missing comma.

Now, if JSON parsing has failed, it will show the place where the issue is:

Unexpected string in JSON at position 16
{"some": "json" "that-is": "wrong"}
---------------^

[IvanGoncharov]

@raqystyle Thanks for PR, cool feature 👍
I think it's valueable beyound this library.
So it would be great if you release it as NPM package.

I would merge it either way, just one suggestion it would be better if you just wrap JSON.parse.

[ivan-demchenko]

@IvanGoncharov I had the same idea of a separate npm package and already looking into differences between platforms ;)

As to your suggestion, I hope I got your idea correctly ;)

UPD: the PR's been updated

[IvanGoncharov]

@raqystyle Looks good for me 👍
@MikeRalphson What do you think?

[MikeRalphson]

Should we allow the optional reviver parameter to be passed through to maintain compatibility?

[ivan-demchenko]

@MikeRalphson I agree. I've started on this little lib, the core idea of which is to just provide a better error message.

[ivan-demchenko]

@IvanGoncharov @MikeRalphson I've updated the PR ;)

[ivan-demchenko]

@MikeRalphson this is a very good point. Fixed ;)