Drop node 16, add node 22

.github/workflows/node.js.yml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [16.x, 18.x, 20.x]
+        node-version: [18.x, 20.x, 22.x]
     steps:
       - uses: actions/checkout@v4
       - name: Use Node.js ${{ matrix.node-version }}

README.md

@@ -29,6 +29,7 @@ Finally, if you want to make this process even less painful, I invite you to che
 
 You can find information about major releases on the [dedicated page](https://github.com/i18next/i18next-parser/releases). The [migration documentation](docs/migration.md) will help you figure out the breaking changes between versions.
 
+- `9.x` is tested on Node 18, 20 and 22.
 - `8.x` is tested on Node 16, 18 and 20.
 - `7.x` is tested on Node 14, 16 and 18.
 - `6.x` is tested on Node 14 and 16.

docs/migration.md

@@ -1,7 +1,9 @@
 # Migrating from `8.x` to `9.x`
 
 ## Breaking changes
-- Support for the `VueLexer` has been dropped as it creates compatibility problems when trying to parse Vue3 code bases.  You must remove any references to `VueLexer` in your configuration files.  For Vue3, you can simply use `JavascriptLexer` instead.
+
+- Support for the `VueLexer` has been dropped as it creates compatibility problems when trying to parse Vue3 code bases. You must remove any references to `VueLexer` in your configuration files. For Vue3, you can simply use `JavascriptLexer` instead.
+- Support for Node 16 is dropped. Node 18, 20 and 22 are supported.
 
 # Migrating from `7.x` to `8.x`
 

package.json

@@ -11,7 +11,7 @@
     "i18next": "./bin/cli.js"
   },
   "engines": {
-    "node": ">=16.0.0 || >=18.0.0 || >=20.0.0",
+    "node": ">=18.0.0 || >=20.0.0 || >=22.0.0",
     "npm": ">=6",
     "yarn": ">=1"
   },