Expose luaparse encoding mode option to lua-in-js

[DanWaLes]

When trying to execute the strings '▲' or '▼' (html entities &#9650 and &#9660), luaparse gives an encoding error. lua-in-js should provide the option to change from the default encoding mode.

[Elly2018]

My scripts have chinese characters in it. It also throw the same error to me as well.
I think the problem is here...

src/parser.ts

encodingMode: 'x-user-defined'

[Gurimarukin]

Downgrading to 2.2.0 fixed it for me.
encodingMode: 'x-user-defined' was introduced in 2.2.1.

[teoxoy]

I should have probably used encodingMode: 'none', could you give it a try? If it works, a PR would be welcome.

[Elly2018]

#24

[teoxoy]

Actually, encodingMode: 'none' is not correct since it always sets value to null, we could use the raw property but we'd have to reparse the string literal ourselves.

'pseudo-latin1' seems like the best choice, but characters outside of ISO/IEC 8859-1 need to be escaped (via \u{XXX}) either by lua-in-js or by user code.

This should also now be removed:

lua-in-js/src/parser.ts

Line 224 in 1165827

.replace(/([^\\])?\\(\d{1,3})/g, (_, pre, dec) => `${pre || ''}${String.fromCharCode(dec)}`)

Relevant: fstirlitz/luaparse#68. Ideally luaparse would allow for a utf16 encoding, but I don't know what that would entail.