A while back, I got a bug report for json-to-multicsv. The user was getting the following error for any input file, including the one used as an example in the documentation: , or } expected while parsing object/hash, at character offset 2 (before "n") The full facts of the matter were: The JSON parser was failing on the third character of the file. That was also the end of the first line in the file. (I.e. the first line of the JSON file contained just the opening bracket). The user was runn...
