Skip to content

v1.0.0-alpha.1

Pre-release
Pre-release

Choose a tag to compare

@bjohansebas bjohansebas released this 08 Jan 16:58
6366ccb

⚠️ Breaking changes

  • 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:

    • A6D9–A6DF: Assigned 7 vertical presentation punctuation characters (︐︒︑︓︔︕︖) that were previously unmapped
    • A6EC–A6ED: Assigned 2 presentation characters (︗︘) that were previously unmapped
    • A6F3: Assigned a punctuation character (︙) that was previously unmapped
    • FE50: Inserted characters 龴, 龵, 龶, 龷, 龸, 龹 at specific positions in the sequence
    • FE80: Inserted characters 龺, 龻 at specific positions in the sequence

Other changes

New Contributors

Full Changelog: v0.7.2...v1.0.0-alpha.1