Version 5

.changeset/curvy-crabs-play.md

@@ -5,4 +5,4 @@
 '@apollo/server': major
 ---
 
-Drop support for Node 14
+Drop support for Node 14 and Node 16

.circleci/config.yml

@@ -139,7 +139,6 @@ workflows:
           matrix:
             parameters:
               node-version:
-                - "16"
                 - "18"
                 - "20"
       - "Check for FIXM\x45"

docs/source/getting-started.mdx

@@ -10,7 +10,7 @@ This tutorial helps you:
 - Run an instance of Apollo Server that lets you execute queries against your schema
 
 This tutorial assumes that you are familiar with the command line and
-JavaScript and have installed a recent Node.js (v16.14.0+) version. Additionally, for those interested, this tutorial includes an optional section describing how to set up Apollo Server with TypeScript.
+JavaScript and have installed a recent Node.js (v18.0.0+) version. Additionally, for those interested, this tutorial includes an optional section describing how to set up Apollo Server with TypeScript.
 
 ## Step 1: Create a new project
 

docs/source/migration.mdx

@@ -14,13 +14,11 @@ While Apollo Server v4 came with numerous breaking changes, the Apollo Server te
 
 ### Node.js
 
-Apollo Server 5 supports Node.js 16.14.0 and later. (Apollo Server 4 supports Node.js 14.16.0.) This includes all LTS and Current major versions at the time of release.
+Apollo Server 5 supports Node.js 18.0.0 and later. (Apollo Server 4 supports Node.js 14.16.0.) This includes all LTS and Current major versions at the time of release.
 
 If you're using Node.js 14, upgrade your runtime before upgrading to Apollo Server 5.
 
-(Apollo Server 5 specifically requires v16.14.0 instead of v16.0.0, because that is the minimum version of Node.js 16 supported by the transitive [`lru-cache` dependency](https://github.com/isaacs/node-lru-cache/commit/c237c1d64ebc2142da4f8324adb3ef300b0428bd), which makes use of `AbortController`.)
-
-If upgrading to Node.js 16 is not possible, you can upgrade to or continue to use Apollo Server 4 without issue.
+If upgrading to Node.js 18 is not possible, you can upgrade to or continue to use Apollo Server 4 without issue.
 
 ## Default behavior change
 

docs/source/using-federation/apollo-gateway-setup.mdx

@@ -17,7 +17,7 @@ Regardless of which graph router library you start with, you can swap to the oth
 
 ## Node.js gateway setup
 
-This section walks through setting up a basic graph router using Apollo Server and the `@apollo/gateway` library. It currently requires [Node.js version 14 or 16](https://nodejs.org/en/download/).
+This section walks through setting up a basic graph router using Apollo Server and the `@apollo/gateway` library. It currently requires [Node.js version >=14.15.0](https://nodejs.org/en/download/).
 
 Create a new Node.js project with `npm init`, then install the necessary packages:
 

package.json

@@ -34,8 +34,8 @@
     "packages/*"
   ],
   "engines": {
-    "node": ">=16.14.0",
-    "npm": ">=8.19.2"
+    "node": ">=18",
+    "npm": ">=9"
   },
   "devDependencies": {
     "@apollo/client": "3.7.17",
@@ -60,7 +60,7 @@
     "@types/lodash.sumby": "4.6.7",
     "@types/lodash.xorby": "4.7.7",
     "@types/negotiator": "0.6.1",
-    "@types/node": "16.18.21",
+    "@types/node": "18.17.1",
     "@types/node-fetch": "2.6.4",
     "@types/qs-middleware": "1.0.1",
     "@types/retry": "0.12.2",

packages/integration-testsuite/package.json

@@ -23,7 +23,7 @@
   },
   "homepage": "https://github.com/apollographql/apollo-server#readme",
   "engines": {
-    "node": ">=16.14.0"
+    "node": ">=18"
   },
   "dependencies": {
     "@apollo/cache-control-types": "^1.0.3",

packages/plugin-response-cache/package.json

@@ -29,7 +29,7 @@
   },
   "homepage": "https://github.com/apollographql/apollo-server#readme",
   "engines": {
-    "node": ">=16.14.0"
+    "node": ">=18"
   },
   "dependencies": {
     "@apollo/utils.createhash": "^3.0.0",

packages/server/package.json

@@ -122,7 +122,7 @@
   },
   "homepage": "https://github.com/apollographql/apollo-server#readme",
   "engines": {
-    "node": ">=16.14.0"
+    "node": ">=18"
   },
   "dependencies": {
     "@apollo/cache-control-types": "^1.0.3",

packages/server/src/plugin/drainHttpServer/index.ts

@@ -32,6 +32,7 @@ export function ApolloServerPluginDrainHttpServer(
     async serverWillStart() {
       return {
         async drainServer() {
+          // FIXME: with Node 18 can we resolve this?
           // Note: we don't use `AbortSignal.timeout()` here because our
           // polyfill doesn't support it (and even once we drop Node v14
           // support, if we don't require at least Node v16.14 then the built-in

packages/server/src/plugin/usageReporting/plugin.ts

@@ -313,6 +313,7 @@ export function ApolloServerPluginUsageReporting<TContext extends BaseContext>(
           // Retry on network errors and 5xx HTTP
           // responses.
           async () => {
+            // FIXME: resolve this with Node 18
             // Note that once we require Node v16 we can use its global
             // AbortController instead of the one from `node-abort-controller`.
             const controller = new AbortController();

renovate.json5

@@ -48,11 +48,11 @@
       matchPaths: ["packages/integration-testsuite/package.json"],
       rangeStrategy: "pin",
     },
-    // We need to support Node v16, so we don't allow ourselves to use type definitions
-    // that would let us write >v16-specific code.
+    // We need to support Node v18, so we don't allow ourselves to use type definitions
+    // that would let us write >v18-specific code.
     {
       matchPackageNames: ["@types/node"],
-      allowedVersions: "16.x"
+      allowedVersions: "18.x"
     },
     // node-fetch v3 only ships as ESM. We currently build as both CommonJS and
     // ESM and we're not going to go ESM-only for a while. So let's stay on v2.