If the last char of a chunk is the escape char, parsing fails.
Defer escape parsing if next char is not in the current chunk
I andrian, thank you for reporting this issue with a patch. I need a testcase illustrating the fix, could you provide me with one?
Fix issue #86: defer escape parsing if next char is not in the curren…
This is fixed, I didn't use your pull request but instead I leverage a mechanism alraedy present inside the parser. Thanks again, I'll publish a new npm version today.
Thanks. My pull request refers to v0.1, though, so your fix doesn't work for me. I'll probably just switch over to master, but if you want to support 0.1.x, you should probably backport the fix.
I don't think many users are still with v0.1, so unless you tell me it will be helpfull for you to backport this fix into an npm release, i will just pass.