From fd53bcaee391f6e4c13df439786d02208fa1d10d Mon Sep 17 00:00:00 2001 From: Antoni Kepinski Date: Sun, 17 May 2020 18:51:24 +0200 Subject: [PATCH 1/2] update beta.6 changelog --- docs/CHANGELOG.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 5fc6fda..28f6fc7 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -7,7 +7,8 @@ Changelog **Work in progress!** -- Fix: Export the `AbortError` class. +- Enhance: improve coverage. +- Fix: export the `AbortError` class. ## v3.0.0-beta.5 From fd62e1a2049dd0c72d818b451b17bb89c05d6d61 Mon Sep 17 00:00:00 2001 From: Antoni Kepinski Date: Sun, 17 May 2020 18:52:09 +0200 Subject: [PATCH 2/2] Kb -> kB --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 23f2c26..5647c93 100644 --- a/README.md +++ b/README.md @@ -491,7 +491,7 @@ const options = { #### Custom highWaterMark -Stream on Node.js have a smaller internal buffer size (16Kb, aka `highWaterMark`) from client-side browsers (>1MB, not consistent across browsers). Because of that, when you are writing an isomorphic app and using `res.clone()`, it will hang with large response in Node. +Stream on Node.js have a smaller internal buffer size (16kB, aka `highWaterMark`) from client-side browsers (>1MB, not consistent across browsers). Because of that, when you are writing an isomorphic app and using `res.clone()`, it will hang with large response in Node. The recommended way to fix this problem is to resolve cloned response in parallel: