chore: upgrade to node 22 and resolve vulnerable deps

Author: pregnantboy

.devcontainer/devcontainer.json

@@ -3,7 +3,7 @@
 {
   "name": "Node.js & TypeScript",
   // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
-  "image": "mcr.microsoft.com/devcontainers/typescript-node:0-18",
+  "image": "mcr.microsoft.com/devcontainers/typescript-node:22",
 
   "forwardPorts": [3000, 3001, 5432, 6379],
   "customizations": {

.github/workflows/test-and-build.yml

@@ -11,7 +11,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
-          node-version: '18'
+          node-version: '22'
           cache: 'npm'
           cache-dependency-path: package-lock.json
       - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."

.nvmrc

@@ -1 +1 @@
-v18.14.2
+v22.19.0

Dockerfile

@@ -1,5 +1,5 @@
 # syntax=docker/dockerfile:1
-FROM node:18-alpine as build
+FROM node:22-alpine as build
 
 ARG APP_ENV=prod
 ENV VITE_MODE=$APP_ENV
@@ -11,7 +11,7 @@ RUN --mount=type=secret,id=NPM_TASKFORCESH_TOKEN \
 RUN npm run build
 RUN npm prune --production
 
-FROM node:18-alpine as main
+FROM node:22-alpine as main
 
 WORKDIR /opt/plumber