Support unescaped UTF newlines if it is in an JSON

[TimothyGu]

Fixes #5.

[alubbe]

why did we want parseObj to throw .parse exceptions in the past but now we catch them?

[TimothyGu]

Before:

read file  ------------------+
   | works      doesn't work |                                                  
   v                         v    doesn't work
JSON.parse --------+       eval ---------------+
   | works  doesn't| work    |                 |   
   v               |         | works           |   
output <-----------+---------+                 |   
                   |                           v   
                   +-----------------------> throw

What's the problem? If the object is specified as a JSON string, and if eval doesn't work, we didn't try JSON.parse. Same thing but reversed with a file: if JSON.parse doesn't work, we didn't try eval.

So, I consolidated the string generation (either reading a file or using the argument verbatim as a string), and consolidated the parsing part (JSON.parse or eval).

Now:

   +------ read file --------+
   | works      doesn't work |
   +-----------+-------------|
               |  
               v         works
           JSON.parse ----------> output
               |   doesn't work
               v  
             eval     ----------> output 
               |   doesn't work
               v  
             throw

[alubbe]

So basically, if JSON.parse on the file's content fails, we now want to just eval said content, right? Then I'm all good with it.

[TimothyGu]

Yep