From 278dfef04d9506f4e804fa20b822101d774ad006 Mon Sep 17 00:00:00 2001 From: Joyee Cheung Date: Thu, 25 Apr 2024 22:04:03 +0200 Subject: [PATCH] fixup! fixup! zlib: expose zlib.crc32() --- doc/api/zlib.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/zlib.md b/doc/api/zlib.md index bd7fb5b138935d..590e3d90cbfa5b 100644 --- a/doc/api/zlib.md +++ b/doc/api/zlib.md @@ -736,10 +736,10 @@ be encoded with UTF-8 before being used for computation. If users only uses Node.js to compute and check the checksums, this works well with other APIs that uses the UTF-8 encoding by default. -Some third-party JavaScript libraries that compute the checksum on a +Some third-party JavaScript libraries compute the checksum on a string based on `str.charCodeAt()` so that it can be run in browsers. If users want to match the checksum computed with this kind of library -from the browser, it's better to use the same library in Node.js +in the browser, it's better to use the same library in Node.js if it also runs in Node.js. If users have to use `zlib.crc32()` to match the checksum produced by such a third-party library: