+1, I use .read() but ya i agree there's no good reason we shouldn't be able to pass an object to .parse(), though it currently works off of the JSON.parse reviver function
I'm currently just doing a JSON.stringify on my object and send it to eson. Which isn't the most pretty way of doing things, but it get the job done.
Parsing objects wouldn't be to hard to add, as long we don't hit any recursion.
for now we could just .stringify in .parse() so it's at least encapsulated and then if we need better perf fix it later. I only use it for config files right now so that part definitely doesn't matter to me ATM
I'll prepare a pull request and some tests for it
The parser should also accept objects instead of strings only. Fixes #6