Update version of node template

Signed-off-by: Han Verstraete (OpenFaaS Ltd) <han@openfaas.com>

Author: welteki

docs/architecture/invocations.md

@@ -22,11 +22,11 @@ Whenever you run `faas-cli build` or `faas-cli publish` using one of the OpenFaa
 Templates tend to abstract away the Dockerfile and entry-point HTTP server from you, so that you can focus on writing a HTTP or function handler, they are still there however and you can look into the "template" folder to find them after running `faas-cli template store pull`
 
 ```bash
-$ faas-cli template store pull node20
-$ ls template/node20
+$ faas-cli template store pull node22
+$ ls template/node22
 Dockerfile      function        index.js        package.json    template.yml
 
-$ ls template/node20/
+$ ls template/node22/
 handler.js      package.json
 ```
 

docs/cli/build.md

@@ -152,8 +152,8 @@ Create a function:
 
 ```bash
 export OPENFAAS_PREFIX=openfaasltd
-faas-cli template store pull node20
-faas-cli new --lang node20 withprivatenpm
+faas-cli template store pull node22
+faas-cli new --lang node22 withprivatenpm
 ```
 
 You will need to create an authentication token to install private npm modules. These instructions will differ depending on the registry you want to use:
@@ -186,7 +186,7 @@ provider:
   gateway: http://127.0.0.1:8080
 functions:
   withprivatenpm:
-    lang: node20
+    lang: node22
     handler: ./withprivatenpm
     image: openfaasltd/withprivatenpm:latest
     build_secrets:
@@ -199,7 +199,7 @@ Run a build with:
 faas-cli pro build -f stack.yml
 ```
 
-You'll also need an updated version of the node template to mount the secret passed in from the OpenFaaS Pro plugin. Update `template/node20/Dockerfile` and replace the second `npm i` command with:
+You'll also need an updated version of the node template to mount the secret passed in from the OpenFaaS Pro plugin. Update `template/node22/Dockerfile` and replace the second `npm i` command with:
 
 ```Dockerfile
 RUN --mount=type=secret,id=npmrc,mode=0666,dst=/home/app/.npmrc npm i

docs/cli/templates.md

@@ -56,7 +56,7 @@ dockerfile               [x]         openfaas           Classic Dockerfile templ
 dotnet8-csharp           [x]         openfaas           C# template using WebApplication
 golang-middleware        [x]         openfaas           HTTP middleware interface in Go
 java11-vert-x            [x]         openfaas           Java 11 Vert.x template
-node20                   [x]         openfaas           HTTP-based Node 18 template
+node22                   [x]         openfaas           HTTP-based Node 22 template
 php8                     [x]         openfaas           Classic PHP 8 template
 python3-http             [x]         openfaas           Python 3 with Flask and HTTP
 python3-http-debian      [x]         openfaas           Python 3 with Flask and HTTP based on Debian

docs/languages/custom.md

@@ -30,7 +30,7 @@ This will include code submitted by a third party. It may or may not be kept up
 
 ### Make your own template
 
-The easiest way to write a template for OpenFaaS it to copy an official template, and to modify it. This example creates a template using Bun and Express.js which is based upon the official node20 template.
+The easiest way to write a template for OpenFaaS it to copy an official template, and to modify it. This example creates a template using Bun and Express.js which is based upon the official 22 template.
 
 Create a new folder called my-templates, it should have a sub-directory within it called `template`.
 
@@ -57,12 +57,12 @@ Next, create a Dockerfile which should download and make available the OpenFaaS
 
 There are two watchdogs available, the [Classic Watchdog](https://github.com/openfaas/classic-watchdog), meant for processes which do not have their own HTTP server, the process will be forked for each request, and the [of-watchdog](https://github.com/openfaas/of-watchdog) for when a HTTP server is available. Since Bun used with Express.js provides a HTTP server, we'll be using the of-watchdog. 
 
-The following Dockerfile is based upon the node20 template, adapted for Bun.
+The following Dockerfile is based upon the node22 template, adapted for Bun.
 
 The `--platform=${TARGETPLATFORM:-linux/amd64}` directive is required for multi-arch support, to make the template work for 64-bit Arm as well as regular *x86_64* machines. Most images that you find on the Docker Hub will already have multi-arch support, and it's strongly recommended to keep it in place.
 
 ```Dockerfile
-FROM --platform=${TARGETPLATFORM:-linux/amd64} ghcr.io/openfaas/of-watchdog:0.9.11 as watchdog
+FROM --platform=${TARGETPLATFORM:-linux/amd64} ghcr.io/openfaas/of-watchdog:0.10.9 as watchdog
 FROM --platform=${TARGETPLATFORM:-linux/amd64} oven/bun:alpine as ship
 
 ARG TARGETPLATFORM
@@ -254,12 +254,7 @@ const middleware = async (req, res) => {
     });
 };
 
-app.post('/*', middleware);
-app.get('/*', middleware);
-app.patch('/*', middleware);
-app.put('/*', middleware);
-app.delete('/*', middleware);
-app.options('/*', middleware);
+app.use(middleware)
 
 const port = process.env.http_port || 3000;
 

docs/languages/node.md

@@ -4,7 +4,7 @@ The [Node.js](https://nodejs.org/en) template for OpenFaaS uses [Express.js](htt
 
 !!! info "Do you need to customise this template?"
 
-    You can customise the official templates, or provide your own. The code for this templates is available on GitHub: [openfaas/templates](https://github.com/openfaas/templates/tree/master/template/node20).
+    You can customise the official templates, or provide your own. The code for this templates is available on GitHub: [openfaas/templates](https://github.com/openfaas/templates/tree/master/template/node22).
 
 The event is used to obtain the original HTTP request, and the context is used to set the HTTP response. The underlying Express.js object is an implementation detail, and so is not available to the function author.
 
@@ -20,7 +20,7 @@ Create a new function using the template:
 
 ```bash
 faas-cli template pull
-faas-cli new --lang node20 echo
+faas-cli new --lang node22 echo
 ```
 
 You'll find a new folder called `echo` with a `handler.js` and `package.json` file inside.
@@ -68,7 +68,7 @@ Or to combine the `context.status()` method with the `context.succeed()` method
 To install packages, `cd` into the function folder and run `npm install --save`:
 
 ```bash
-faas-cli new --lang node20 http-req
+faas-cli new --lang node22 http-req
 cd http-req
 
 npm install --save axios
@@ -132,12 +132,12 @@ Then create a new secret in OpenFaaS:
 faas-cli secret create node-fn-token --from-file node-fn-token.txt
 ```
 
-Create a new function using the *node20* template:
+Create a new function using the *node22* template:
 
 ```bash
 export OPENFAAS_PREFIX=ttl.sh/fns
 
-faas-cli new --lang node20 node-fn
+faas-cli new --lang node22 node-fn
 ```
 
 Then edit the `node-fn/handler.js`:
@@ -176,7 +176,7 @@ Edit `node-fn.yml` and add the `secrets` section:
 ```diff
 functions:
   node-fn:
-    lang: node20
+    lang: node22
     handler: ./node-fn
     image: ttl.sh/fns/node-fn:latest
 +    secrets:
@@ -210,7 +210,7 @@ When you test the function with `faas-cli up`, make sure you use the function's
 
 Unit tests provide a quick and efficient way to exercise your code on your local computer, without needing to run `faas-cli build` or to deploy the function to a remote cluster.
 
-With the node20 template, any unit tests that you provide will be run automatically upon each invocation of `faas-cli build`.
+With the node22 template, any unit tests that you provide will be run automatically upon each invocation of `faas-cli build`.
 
 
 By default, an empty test step is written to package.json inside your function's handler folder, you can override this with your own command or test runner.
@@ -305,7 +305,7 @@ The OpenTelemetry agent can be configured using environment variables on the fun
 ```diff
 functions:
   echo:
-    lang: node20
+    lang: node22
     handler: ./node
     image: echo:latest
 +    environment:

docs/openfaas-pro/builder.md

@@ -119,7 +119,7 @@ mkdir -p /tmp/functions
 cd /tmp/functions
 
 # Create a new function
-faas-cli new --lang node20 hello-world
+faas-cli new --lang node22 hello-world
 
 # The shrinkwrap command performs the templating 
 # stage, then stops before running "docker build"
@@ -278,7 +278,7 @@ You may need to enable build arguments for the Dockerfile, these can be passed t
 {
   "image": "ttl.sh/alexellis/test-image:0.1.0",
   "buildArgs": {
-    "BASE_IMAGE": "gcr.io/quiet-mechanic-140114/openfaas-base/node20"
+    "BASE_IMAGE": "gcr.io/quiet-mechanic-140114/openfaas-base/node22"
   }
 }
 ```

docs/openfaas-pro/kafka-events.md

@@ -77,7 +77,7 @@ Most templates make these variables available through their request or context o
 
 * [golang-middleware](/languages/go/)
 * [python3-http](/languages/python/)
-* [node20](/languages/node/)
+* [node22](/languages/node/)
 
 For detailed examples with Node.js, see: [Serverless For Everyone Else](http://store.openfaas.com/l/serverless-for-everyone-else)