Closed Redsandro closed 9 years ago
Also, this error doesn't seem get handled properly. It stops the node even in a try-catch. I'm not sure what exactly is going on so I'm not sure why.
I reproduced the issue, thanks.
This issue should be fixed now; please install 0.0.9 which has just been published to npm.
It seems to work now.
Could you humor me and explain what the problem was?
Ah, I see it of course in the diff. :smile:
Not sure how this works, but can the code somehow be run in a try
so that the node module throws an error if anything unexpected happens?
This would make node stay alive which is important in production environments.
using a simple
(The xml is fine.)
@damirn said:
I tried many pieces of xml, but here is an example: