Skip to content

Drop support for Node.js <=22.11 #1626

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rowanmanning merged 1 commit into from
Jan 12, 2026
Merged

Drop support for Node.js <=22.11 #1626

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 16 additions & 16 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@
"typescript": "^5.9.3"
},
"engines": {
"node": "22.x || 24.x"
"node": "^22.12 || ^24"
},
"volta": {
"node": "24.12.0"
Expand Down
5 changes: 5 additions & 0 deletions packages/app-info/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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).
2 changes: 1 addition & 1 deletion packages/app-info/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
5 changes: 5 additions & 0 deletions packages/client-metrics-web/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
2 changes: 1 addition & 1 deletion packages/client-metrics-web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down
5 changes: 5 additions & 0 deletions packages/crash-handler/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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).
2 changes: 1 addition & 1 deletion packages/crash-handler/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down
5 changes: 5 additions & 0 deletions packages/errors/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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).
2 changes: 1 addition & 1 deletion packages/errors/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
5 changes: 5 additions & 0 deletions packages/eslint-config/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -52,3 +53,7 @@ You may need to make changes to your code if these linting errors are found.
### 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).
2 changes: 1 addition & 1 deletion packages/eslint-config/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: eslint-config\"",
"license": "MIT",
"engines": {
"node": "22.x || 24.x"
"node": "^22.12 || ^24"
},
"main": "lib/index.js",
"types": "types/index.d.ts",
Expand Down
5 changes: 5 additions & 0 deletions packages/fetch-error-handler/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,15 @@ Emoji | Label | Meaning

* [Migrating from v1 to v2](#migrating-from-v1-to-v2)
* [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

### 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).
2 changes: 1 addition & 1 deletion packages/fetch-error-handler/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: fetch-error-handler\"",
"license": "MIT",
"engines": {
"node": "22.x || 24.x"
"node": "^22.12 || ^24"
},
"main": "lib/index.js",
"types": "types/index.d.ts",
Expand Down
5 changes: 5 additions & 0 deletions packages/log-error/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -72,3 +73,7 @@ logHandledError({
### 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).
2 changes: 1 addition & 1 deletion packages/log-error/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: log-error\"",
"license": "MIT",
"engines": {
"node": "22.x || 24.x"
"node": "^22.12 || ^24"
},
"main": "lib/index.js",
"types": "types/index.d.ts",
Expand Down
5 changes: 5 additions & 0 deletions packages/logger/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,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 n-logger
Expand Down Expand Up @@ -311,3 +312,7 @@ If neither of the above is true, this should be a safe update with no code chang
### 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).
2 changes: 1 addition & 1 deletion packages/logger/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: logger\"",
"license": "MIT",
"engines": {
"node": "22.x || 24.x"
"node": "^22.12 || ^24"
},
"main": "lib/index.js",
"types": "types/index.d.ts",
Expand Down
5 changes: 5 additions & 0 deletions packages/middleware-allow-request-methods/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,15 @@ Emoji | Label | Meaning

* [Migrating from v1 to v2](#migrating-from-v1-to-v2)
* [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

### 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).
2 changes: 1 addition & 1 deletion packages/middleware-allow-request-methods/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"bugs": "https://github.com/Financial-Times/dotcom-reliability-kit/issues?q=label:\"package: middleware-allow-request-methods\"",
"license": "MIT",
"engines": {
"node": "22.x || 24.x"
"node": "^22.12 || ^24"
},
"main": "lib/index.js",
"types": "types/index.d.ts"
Expand Down
5 changes: 5 additions & 0 deletions packages/middleware-log-errors/docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -75,3 +76,7 @@ You can safely migrate to this version of the error logging middleware if your a
### 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).
Loading