Alexander Shtuchkin

Short version: don't have to time to create and maintain a separate piece of code. Please use browserify or similar. On Sun, Feb 16, 2020 at 10:17 PM WonderZC wrote:...

Just follow instructions on https://browserify.org/ and import iconv-lite there.

Sorry I don't have time to create a full fledged example at this time. Maybe someone from the community can help you. Or you can try posting this question in...

First of all, I'm impressed by the quality of the pull requests you produce: improved README, tests, the code itself are all top notch. Great job Kerry! In the past,...

AFAIK, you just need to install node-iconv yourself for encoding module to use it. Let me know if it helped. ISO-2022-JP is a rare encoding nowadays and is quite different...

Got it! Thanks ## Alexander Shtuchkin On Mon, Dec 1, 2014 at 8:24 AM, coyle [email protected] wrote: > I'll throw my vote in here. Just ran into the same error....

string_decoder is a core nodejs module ( https://nodejs.org/api/string_decoder.html). Please check your build environment. On Fri, Mar 18, 2022, 03:21 NguyenHuynhHuuTai ***@***.***> wrote: > BUNDLE ./index.js > > error: Error: Unable...

We currently have `iconv.encodingExists` which can help in some cases, but I can see the value in having an official way to list encodings, yes. I'll try to add it...

That's a different API. iconv-lite doesn't even have this information at this point.

Well, an obvious idea would be to create such a mapping yourself and potentially publish a npm module. At this point, I don't think it's a great fit for iconv-lite.