chore!: drop support for Node.js <=22.11

Node.js 22.12 removes the need for the `--experimental-require-module`
CLI flag when importing native ESM into CommonJS contexts. We'd like to
migrate Reliability Kit to be ESM and we'd like for the teams who use it
to not have to include this CLI flag.

We're taking the decision to drop support for Node.js versions below
22.12 in order to support this.

This is the first step towards us migrating to native ESM, see #1479.

Author: rowanmanning

package-lock.json

@@ -45,7 +45,7 @@
     "typescript": "^5.9.3"
   },
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "volta": {
     "node": "24.12.0"

package.json

@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -44,3 +45,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).

packages/app-info/docs/migration.md

@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: app-info\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts"

packages/app-info/package.json

@@ -11,10 +11,15 @@ Emoji           | Label             | Meaning
 
 * [Migrating from v0 to v1](#migrating-from-v0-to-v1)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v0 to v1
 
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).

packages/client-metrics-web/docs/migration.md

@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: client-metrics-web\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",

packages/client-metrics-web/package.json

@@ -19,6 +19,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v5 to v6](#migrating-from-v5-to-v6)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -73,3 +74,7 @@ You can safely migrate to this version of Crash Handler if your app is either _n
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).

packages/crash-handler/docs/migration.md

@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: crash-handler\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts",

packages/crash-handler/package.json

@@ -16,6 +16,7 @@ Emoji           | Label             | Meaning
   * [Node.js 18 is no longer supported](#nodejs-18-is-no-longer-supported)
 * [Migrating from v4 to v5](#migrating-from-v4-to-v5)
   * [Node.js 20 is no longer supported](#nodejs-20-is-no-longer-supported)
+  * [Node.js 22.11 is no longer supported](#nodejs-2211-is-no-longer-supported)
 
 
 ## Migrating from v1 to v2
@@ -44,3 +45,7 @@ Emoji           | Label             | Meaning
 ### Node.js 20 is no longer supported
 
 **:red_circle: Breaking:** this version drops support for Node.js v20. If your app is already using Node.js v22 then you may be able to migrate without code changes.
+
+### Node.js 22.11 is no longer supported
+
+**:red_circle: Breaking:** this version drops support for Node.js v22.11 or lower. If your app is already using Node.js v22.12 then you may be able to migrate without code changes. This is so that we can publish native ESM modules without requiring complex changes in our consuming applications. [See #1479 for more information](https://github.com/Financial-Times/dotcom-reliability-kit/issues/1479).

packages/errors/docs/migration.md

@@ -11,7 +11,7 @@
   "bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: errors\"",
   "license": "MIT",
   "engines": {
-    "node": "22.x || 24.x"
+    "node": "^22.12 || ^24"
   },
   "main": "lib/index.js",
   "types": "types/index.d.ts"