Timeout requests and stop processing further

.github/workflows/tests.yaml

@@ -81,7 +81,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [16.x]
+        node-version: [18.x]
 
     services:
       # We need two homeservers that federate with each other to test with

Dockerfile

@@ -2,7 +2,7 @@
 # with error 243 issues are solved:
 #  - https://github.com/npm/cli/issues/4996
 #  - https://github.com/npm/cli/issues/4769
-FROM node:16.14.2-buster-slim
+FROM node:18.16.0-buster-slim
 
 # Pass through some GitHub CI variables which we use in the build (for version
 # files/tags)

README.md

@@ -35,11 +35,16 @@ See the [FAQ page](docs/faq.md).
 
 ### Prerequisites
 
-- [Node.js](https://nodejs.org/) v16
-  - We only need v16 because it includes
+- [Node.js](https://nodejs.org/) v18
+  - We need v18 because it includes `fetch` by default. And [`node-fetch` doesn't
+    support `abortSignal.reason`](https://github.com/node-fetch/node-fetch/issues/1462)
+    yet.
+  - We need v16 because it includes
     [`require('crypto').webcrypto.subtle`](https://nodejs.org/docs/latest-v16.x/api/webcrypto.html#cryptosubtle)
     for [Matrix encryption (olm) which can't be disabled in
-    Hydrogen](https://github.com/vector-im/hydrogen-web/issues/579) yet.
+    Hydrogen](https://github.com/vector-im/hydrogen-web/issues/579) yet. And
+    [`abortSignal.reason` was introduced in
+    v16.14.0](https://nodejs.org/dist/latest-v18.x/docs/api/globals.html#abortsignalreason) (although we use `node-fetch` for now).
 - A Matrix homeserver that supports [MSC3030's](https://github.com/matrix-org/matrix-spec-proposals/pull/3030) `/timestamp_to_event` endpoint
   - [Synapse](https://matrix.org/docs/projects/server/synapse) 1.73.0+