Also, would you mind adding support to the `nodeToCharCode` function at the end of the line for ES6 Unicode code points? There are no unit tests for the `nodeToCharCode` yet in the parser, which should either change or the `nodeToCharCode` moves out of the parser file/remove it from the repo at all.

Personally, I would love to keep it in the repo, as I see value for consumers of the parser to be able to convert the escaped value into a "normalized" charCode representation.

Thoughts?