Repository navigation
Iconv-lite v1 #370
Description
I’m opening this issue to complete the backlog for this new major version.
- Fix the spec:
- Encodings used in iconv-lite mismatch the WHATWG Encoding spec significantly #367
- Replacement in single-byte encodings should not produce two output bytes per one input codepoint #368
- utf-8 is incorrect when used in browsers or React Native #369
- U+301C and U+FF5E are not correctly mapped in EUC-JP/Shift_JIS/CP932 #145
- TextDecoder and Web streams #340
- Support using Uint8Array as the "bytes" data type (instead of Buffer) #235
I want to start releasing alpha versions while I work on this release, so we can see how much we’ve improved in terms of compatibility with the specification.
Pull Request of v1: https://github.com/pillarjs/iconv-lite/pulls?q=is%3Apr+is%3Aopen+label%3Av1
Activity
GroophyLifefor commentedon Feb 6, 2026
Hi Sebastian, is #235 not solved with 7a64f21 ? Or might I'm missing some parts.
bjohansebas commentedon Feb 6, 2026
Hey, we no longer need to have backerns. That was necessary when this version was being developed (it targeted Node >4, and TextDecoder support didn’t exist yet). Now the idea is to migrate everything to avoid using Node.js buffers and instead use things like Uint8Array
GroophyLifefor commentedon Feb 7, 2026
Great, I've read almost all of the comments about the Buffer being inconsistent, and since the decision has already been made, I would love to work on it.
edit: Switching to Uint8Array seems harder than I thought 😄
bjohansebas commentedon Feb 7, 2026
haha yeah, don’t try to do everything in a single PR, do it in separate ones. That also makes it easier for me to review. As for UTF-16, I think we could probably rely only on TextDecoder for the decoder; I haven’t checked yet whether the inconsistencies that existed before are still there.
bjohansebas commentedon Oct 31, 2026
P.S. I’m almost done making the changes to the public API so we can release a beta