Merged
Conversation
Pull Request Test Coverage Report for Build 20754367386Details
💛 - Coveralls |
This was
linked to
issues
Jan 6, 2026
UlisesGascon
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I plan to release this alpha version on January 8. The reason for this is to start comparing our progress with the specification, and also because more breaking changes are coming. cc: @pillarjs/express-tc @pillarjs/iconv-lite-collaborators
Tag: https://github.com/pillarjs/iconv-lite/releases/edit/untagged-281e80ec31c9ea2a7297
Remove support for Node <18 and safe-buffer dependency - by @bjohansebas @Phillip9587 and @TheThing in #265 and #349
Node.js versions prior to 18 are no longer supported. This allows us to remove the safe-buffer dependency and use native Buffer methods available in Node 18 and later.
Use native TextDecoder for decoding - by @JohnGu9 and @bjohansebas in #316
While this improves compatibility with web standards, some edge cases may behave differently because the implementation of TextDecoder in Node.js or other JavaScript runtimes has issues with the specification.
🚀 Improvements
Introduce backend abstraction layer to support to Uint8Array buffer implementation - by @ashtuchkin
This paves the way for supporting environments without Node.js Buffer, such as browsers using Uint8Array.
This is a work in progress, so many parts still rely on Buffer internally, but the goal is to eventually have full support for a Uint8Array based implementation.
Update of the GBK encoding table according to changes in the specification - by @bjohansebas in #371
The GBK encoding table was updated to reflect the latest changes in the Encoding Standard:
What's Changed
New Contributors
Full Changelog: v0.7.1...v1