natevw/node-chargify — pull request #2 by willwhite (2012-12-04 20:10:51+00:00)
Title: Stricter JSON parse when content-type header is application/json.

Just a little fix to address a problem we had during the Chargify datacenter migration last weekend. Their API was not returning a complete response and therefore the JSON was invalid. Instead of being caught at the source, the unpatched code would allow the body to slip by as a string, causing potential havoc downstream when code get a string instead of an object.

Would love to get this in a release if you have a moment, @natevw.

Thanks!