Upcoming Release Changes

benchmarks/server/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @benchmarks/server
 
+## 0.0.53
+
+### Patch Changes
+
+- Updated dependencies
+  [[`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)]:
+  - @whatwg-node/[email protected]
+
 ## 0.0.52
 
 ### Patch Changes

benchmarks/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@benchmarks/server",
-  "version": "0.0.52",
+  "version": "0.0.53",
   "type": "module",
   "private": true,
   "scripts": {
@@ -13,7 +13,7 @@
     "test": "start-server-and-test start http://127.0.0.1:4000/ping loadtest"
   },
   "dependencies": {
-    "@whatwg-node/server": "0.10.5"
+    "@whatwg-node/server": "0.10.6"
   },
   "devDependencies": {
     "start-server-and-test": "2.0.11"

e2e/aws-lambda/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @e2e/aws-lambda
 
+## 0.0.41
+
+### Patch Changes
+
+- Updated dependencies
+  [[`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)]:
+  - @whatwg-node/[email protected]
+
 ## 0.0.40
 
 ### Patch Changes

e2e/aws-lambda/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@e2e/aws-lambda",
-  "version": "0.0.40",
+  "version": "0.0.41",
   "private": true,
   "scripts": {
     "build": "node scripts/bundle.js",
     "e2e": "ts-node -r tsconfig-paths/register scripts/e2e.ts"
   },
   "dependencies": {
     "@e2e/shared-scripts": "0.0.0",
-    "@whatwg-node/fetch": "0.10.6",
+    "@whatwg-node/fetch": "0.10.7",
     "aws-lambda": "1.0.7"
   },
   "devDependencies": {

e2e/shared-server/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @e2e/shared-server
 
+## 0.0.142
+
+### Patch Changes
+
+- Updated dependencies
+  [[`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)]:
+  - @whatwg-node/[email protected]
+  - @whatwg-node/[email protected]
+
 ## 0.0.141
 
 ### Patch Changes

e2e/shared-server/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@e2e/shared-server",
-  "version": "0.0.141",
+  "version": "0.0.142",
   "private": true,
   "dependencies": {
-    "@whatwg-node/fetch": "0.10.6",
-    "@whatwg-node/server": "0.10.5"
+    "@whatwg-node/fetch": "0.10.7",
+    "@whatwg-node/server": "0.10.6"
   }
 }

e2e/vercel/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @e2e/vercel
 
+## 0.0.142
+
+### Patch Changes
+
+- Updated dependencies []:
+  - @e2e/[email protected]
+
 ## 0.0.141
 
 ### Patch Changes

e2e/vercel/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@e2e/vercel",
-  "version": "0.0.141",
+  "version": "0.0.142",
   "private": true,
   "scripts": {
     "build": "node scripts/bundle.js",
@@ -12,7 +12,7 @@
   },
   "dependencies": {
     "@e2e/shared-scripts": "0.0.0",
-    "@e2e/shared-server": "0.0.141",
+    "@e2e/shared-server": "0.0.142",
     "encoding": "0.1.13",
     "next": "15.3.2",
     "react": "19.1.0",

packages/fetch/CHANGELOG.md

@@ -1,5 +1,30 @@
 # @whatwg-node/fetch
 
+## 0.10.7
+
+### Patch Changes
+
+- [#2383](https://github.com/ardatan/whatwg-node/pull/2383)
+  [`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)
+  Thanks [@ardatan](https://github.com/ardatan)! - Some implementations like `compression` npm
+  package do not implement `response.write(data, callback)` signature, but whatwg-node/server waits
+  for it to finish the response stream. Then it causes the response stream hangs when the
+  compression package takes the stream over when the response data is larger than its threshold.
+
+  It is actually a bug in `compression` package;
+  [expressjs/compression#46](https://github.com/expressjs/compression/issues/46) But since it is a
+  common mistake, we prefer to workaround this on our end.
+
+  Now after calling `response.write`, it no longer uses callback but first it checks the result;
+
+  if it is `true`, it means stream is drained and we can call `response.end` immediately. else if it
+  is `false`, it means the stream is not drained yet, so we can wait for the `drain` event to call
+  `response.end`.
+
+- Updated dependencies
+  [[`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)]:
+  - @whatwg-node/[email protected]
+
 ## 0.10.6
 
 ### Patch Changes

packages/fetch/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whatwg-node/fetch",
-  "version": "0.10.6",
+  "version": "0.10.7",
   "description": "Cross Platform Smart Fetch Ponyfill",
   "repository": {
     "type": "git",
@@ -16,7 +16,7 @@
   "browser": "dist/global-ponyfill.js",
   "types": "dist/index.d.ts",
   "dependencies": {
-    "@whatwg-node/node-fetch": "^0.7.18",
+    "@whatwg-node/node-fetch": "^0.7.19",
     "urlpattern-polyfill": "^10.0.0"
   },
   "publishConfig": {

packages/node-fetch/CHANGELOG.md

@@ -1,5 +1,30 @@
 # @whatwg-node/node-fetch
 
+## 0.7.19
+
+### Patch Changes
+
+- [#2383](https://github.com/ardatan/whatwg-node/pull/2383)
+  [`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)
+  Thanks [@ardatan](https://github.com/ardatan)! - Some implementations like `compression` npm
+  package do not implement `response.write(data, callback)` signature, but whatwg-node/server waits
+  for it to finish the response stream. Then it causes the response stream hangs when the
+  compression package takes the stream over when the response data is larger than its threshold.
+
+  It is actually a bug in `compression` package;
+  [expressjs/compression#46](https://github.com/expressjs/compression/issues/46) But since it is a
+  common mistake, we prefer to workaround this on our end.
+
+  Now after calling `response.write`, it no longer uses callback but first it checks the result;
+
+  if it is `true`, it means stream is drained and we can call `response.end` immediately. else if it
+  is `false`, it means the stream is not drained yet, so we can wait for the `drain` event to call
+  `response.end`.
+
+- Updated dependencies
+  [[`d86b4f3`](https://github.com/ardatan/whatwg-node/commit/d86b4f3df884709145023bf32bb1022c4a8bb9cb)]:
+  - @whatwg-node/[email protected]
+
 ## 0.7.18
 
 ### Patch Changes

packages/node-fetch/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whatwg-node/node-fetch",
-  "version": "0.7.18",
+  "version": "0.7.19",
   "type": "module",
   "description": "Fetch API implementation for Node",
   "repository": {
@@ -36,7 +36,7 @@
   "dependencies": {
     "@fastify/busboy": "^3.1.1",
     "@whatwg-node/disposablestack": "^0.0.6",
-    "@whatwg-node/promise-helpers": "^1.3.1",
+    "@whatwg-node/promise-helpers": "^1.3.2",
     "tslib": "^2.6.3"
   },
   "devDependencies": {

packages/promise-helpers/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @whatwg-node/promise-helpers
 
+## 1.3.2
+
+### Patch Changes
+
+- [#2408](https://github.com/ardatan/whatwg-node/pull/2408)
+  [`d86b4f3`](https://github.com/ardatan/whatwg-node/commit/d86b4f3df884709145023bf32bb1022c4a8bb9cb)
+  Thanks [@slagiewka](https://github.com/slagiewka)! - Reuse fake promise Symbol
+
 ## 1.3.1
 
 ### Patch Changes

packages/promise-helpers/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whatwg-node/promise-helpers",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "type": "module",
   "description": "Promise helpers",
   "repository": {

packages/server/CHANGELOG.md

@@ -1,5 +1,32 @@
 # @whatwg-node/server
 
+## 0.10.6
+
+### Patch Changes
+
+- [#2383](https://github.com/ardatan/whatwg-node/pull/2383)
+  [`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)
+  Thanks [@ardatan](https://github.com/ardatan)! - Some implementations like `compression` npm
+  package do not implement `response.write(data, callback)` signature, but whatwg-node/server waits
+  for it to finish the response stream. Then it causes the response stream hangs when the
+  compression package takes the stream over when the response data is larger than its threshold.
+
+  It is actually a bug in `compression` package;
+  [expressjs/compression#46](https://github.com/expressjs/compression/issues/46) But since it is a
+  common mistake, we prefer to workaround this on our end.
+
+  Now after calling `response.write`, it no longer uses callback but first it checks the result;
+
+  if it is `true`, it means stream is drained and we can call `response.end` immediately. else if it
+  is `false`, it means the stream is not drained yet, so we can wait for the `drain` event to call
+  `response.end`.
+
+- Updated dependencies
+  [[`d86b4f3`](https://github.com/ardatan/whatwg-node/commit/d86b4f3df884709145023bf32bb1022c4a8bb9cb),
+  [`9527e8f`](https://github.com/ardatan/whatwg-node/commit/9527e8fe2dc73e362b38060f4a6decbb87a4f597)]:
+  - @whatwg-node/[email protected]
+  - @whatwg-node/[email protected]
+
 ## 0.10.5
 
 ### Patch Changes

packages/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whatwg-node/server",
-  "version": "0.10.5",
+  "version": "0.10.6",
   "type": "module",
   "description": "Fetch API compliant HTTP Server adapter",
   "repository": {
@@ -36,8 +36,8 @@
   "dependencies": {
     "@envelop/instrumentation": "^1.0.0",
     "@whatwg-node/disposablestack": "^0.0.6",
-    "@whatwg-node/fetch": "^0.10.6",
-    "@whatwg-node/promise-helpers": "^1.3.1",
+    "@whatwg-node/fetch": "^0.10.7",
+    "@whatwg-node/promise-helpers": "^1.3.2",
     "tslib": "^2.6.3"
   },
   "devDependencies": {