Upgrade Node.js to v22.16.0

.circleci/config.yml

@@ -19,7 +19,7 @@ commands:
 jobs:
   build:
     docker:
-      - image: cimg/node:18.20.4
+      - image: cimg/node:22.16.0
     steps:
       - checkout
       - setup_npm
@@ -32,7 +32,7 @@ jobs:
 
   test:
     docker:
-      - image: cimg/node:18.20.4
+      - image: cimg/node:22.16.0
     steps:
       - checkout
       - setup_npm

.node-version

@@ -1 +1 @@
-18.20.4
+22.16.0

Dockerfile

@@ -1,6 +1,6 @@
 ### Baseline image for development/test/build ###
 # We require a lot of extras for building (Python, GCC) because of Node-Zopfli.
-FROM node:18.20.4 as dev
+FROM node:22.16.0 as dev
 LABEL maintainer="[email protected]"
 
 RUN mkdir -p /app
@@ -30,7 +30,7 @@ RUN npm run build-production
 ### Release Image ###
 # It might feel ridiculous to build up all the same things again, but the
 # resulting image is less than half the size!
-FROM node:18.20.4-slim as release
+FROM node:22.16.0-slim as release
 LABEL maintainer="[email protected]"
 
 RUN apt-get update && apt-get install -y --no-install-recommends dumb-init

README.md

@@ -17,7 +17,7 @@ It’s a React.js-based browser application with a Node.js backend with the foll
 
 ## Installation
 
-1. Install Node 18.20.4.
+1. Install Node 22.16.0.
     - We recommend using [Nodenv][nodenv], which will automatically select the correct version of Node.js to run for you.
         - If you don’t yet have the right version of Node.js installed, enter the root directory for this project and then run `nodenv install`.
     - Alternatively, you can use [NVM][nvm] or a variety of [alternatives][nodenv-alternatives] for managing multiple versions of Node.js.

package.json

@@ -80,7 +80,7 @@
   "author": "",
   "license": "GPL-3.0",
   "engines": {
-    "node": "18.20.4"
+    "node": "22.16.0"
   },
   "browserslist": [
     "last 3 versions",