Use Node.js 22.x in CI and require >=22.10.0 in package.json (#9)

- Changed CI workflows to use node-version '22.x' (latest 22.x)
- Updated engines.node requirement to >=22.10.0
- Updated README to reflect Node 22.10.0+ requirement
- Node 22.9.0 has ESM compatibility issues with vitest; 22.10+ fixes these

Author: peteski22

.github/workflows/lint.yaml

@@ -17,7 +17,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
         with:
-          node-version: '22'
+          node-version: '22.x'
 
       - name: Install npm 11.6.2
         run: npm install -g npm@11.6.2

.github/workflows/release.yaml

@@ -35,7 +35,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
         with:
-          node-version: '22'
+          node-version: '22.x'
           registry-url: 'https://registry.npmjs.org'
 
       - name: Install latest npm

.github/workflows/tests.yaml

@@ -17,7 +17,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
         with:
-          node-version: '22'
+          node-version: '22.x'
 
       - name: Install npm 11.6.2
         run: npm install -g npm@11.6.2

README.md

@@ -26,7 +26,7 @@ An MCP (Model Context Protocol) server that acts as a proxy between IDEs and the
 
 ## Prerequisites
 
-- `Node.js` 22.9.0 or higher
+- `Node.js` 22.10.0 or higher (latest 22.x recommended)
 - `mcpd` daemon running and accessible
 - `mcpd` SDK (automatically installed as a dependency)
 

package-lock.json

@@ -75,7 +75,7 @@
     "vitest": "^4.0.10"
   },
   "engines": {
-    "node": ">=22.9.0"
+    "node": ">=22.10.0"
   },
   "packageManager": "npm@11.6.2"
 }