Use Node's new built-in zstd support for HTTP body where possible

Author: pimterry

.github/workflows/ci.yml

@@ -7,7 +7,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [18.x, 20.x, v20.11.1, '*']
+        node-version: [18.x, 20.x, 22.x, 24.x, '*']
 
     steps:
       - uses: actions/checkout@v2

README.md

@@ -1,10 +1,10 @@
 # http-encoding [![Build Status](https://github.com/httptoolkit/http-encoding/workflows/CI/badge.svg)](https://github.com/httptoolkit/http-encoding/actions) [![Available on NPM](https://img.shields.io/npm/v/http-encoding.svg)](https://npmjs.com/package/http-encoding)
 
-> _Part of [HTTP Toolkit](https://httptoolkit.tech): powerful tools for building, testing & debugging HTTP(S)_
+> _Part of [HTTP Toolkit](https://httptoolkit.com): powerful tools for building, testing & debugging HTTP(S)_
 
 **Everything you need to handle HTTP message body content-encoding**
 
-This package includes methods to decode & encode all commonly used HTTP content encodings, in a consistent format, usable in both Node.js and browsers.
+This package includes methods to decode & encode all commonly used HTTP content encodings, in a consistent format, usable in a wide range of Node.js versions and browsers.
 
 The supported codecs are:
 

package.json

@@ -38,7 +38,7 @@
     "gzip",
     "deflate"
   ],
-  "author": "Tim Perry <tim@httptoolkit.tech>",
+  "author": "Tim Perry <tim@httptoolkit.com>",
   "license": "Apache-2.0",
   "bugs": {
     "url": "https://github.com/httptoolkit/http-encoding/issues"
@@ -56,7 +56,7 @@
     "@types/chai": "^4.2.18",
     "@types/chai-as-promised": "^7.1.4",
     "@types/mocha": "^8.2.2",
-    "@types/node": "^15.3.0",
+    "@types/node": "^22.15.16",
     "@types/pify": "^5.0.1",
     "assert": "^2.0.0",
     "browserify-zlib": "^0.2.0",
@@ -76,7 +76,7 @@
     "stream-browserify": "^3.0.0",
     "ts-loader": "^9.3.1",
     "ts-node": "^10.9.1",
-    "typescript": "4.7.4",
+    "typescript": "^5.8.3",
     "util": "^0.12.3",
     "webpack": "^5.37.0",
     "zlib-browserify": "0.0.3"

src/index.ts

@@ -49,12 +49,39 @@ export const brotliDecompress = zlib.brotliDecompress
         return decompress(buffer);
     });
 
-// Zstd is a non-built-in wasm implementation that initializes async. We handle this by
-// loading it when the first zstd buffer is decompressed. That lets us defer loading
+// Browser Zstd is a non-built-in wasm implementation that initializes async. We handle this
+// by loading it when the first zstd buffer is decompressed. That lets us defer loading
 // until that point too, which is good since it's large-ish & rarely used.
 let zstd: Promise<ZstdStreaming> | undefined;
 const getZstd = async () => {
-    if (!zstd) {
+    // In Node 22.15 / 23.8+, we can use zstd built-in:
+    if (zlib.zstdCompress && zlib.zstdDecompress) {
+        return {
+            compress: (buffer: Uint8Array, level?: number) => {
+                return new Promise<Uint8Array>((resolve, reject) => {
+                    const options = level !== undefined
+                        ? { [zlib.constants.ZSTD_c_compressionLevel]: level }
+                        : {};
+
+                    zlib.zstdCompress(buffer, options, (err, result) => {
+                        if (err) reject(err);
+                        else resolve(result);
+                    });
+                });
+            },
+            decompress: (buffer: Uint8Array) => {
+                return new Promise<Uint8Array>((resolve, reject) => {
+                    zlib.zstdDecompress(buffer, (err, result) => {
+                        if (err) reject(err);
+                        else resolve(result);
+                    });
+                });
+            }
+        };
+    }
+
+    // In older Node and browsers, we fall back to zstd-codec:
+    else if (!zstd) {
         zstd = new Promise(async (resolve) => {
             const { ZstdCodec } = await import('zstd-codec');
             ZstdCodec.run((binding) => {