Azure function and Kudu console NODE version mismatch in linux OS azure function.

[htke1]

I had hard time with my azure function when I try to deploy my function with node 18 lts. The configuration and package.json, linuxfxversion has node 18 lts as shown below.

So when I check the kudu console's NODE version, it is 14.19.2

although npm install is completed without any error. But I face NODE_MODULE_VERSION mismatch error when I trigger the function.

I have tried downgrading my azure configuration to node 14 lts and also changed in package.json to 14 lts. Only then I can run my function. This is not proper as we want our function to run in node 18, and its been happening since 2 years back with other older node version as well.

Do azure function hosted by linux support node 18 lts in kudu? Is there any way I can match the node version of kudu with my function which is node 18 lts. why is it showing mismatch NODE MODULE VERSION? Please help me resolve this.

Azure/azure-functions-host#7485 similar to this issue.

[satvu]

Hi @htke1, Node 18 has been generally available for most of this year and should be supported here - have you followed the instructions linked in the similar issue (setting node version)? I am not entirely sure the screenshots show linuxFxVersion being set correctly since the value should be in "language|languageversion" format according to our wiki page, but will defer to folks from Linux/Node teams to help answer this.

cc: @pragnagopa @ejizba @hossam-nasr

[hossam-nasr]

+1 to what @satvu mentioned here. The ways mentioned in this issue (package.json engines field, FRAMEWORK_VERSION) are not honored in determining node version as far as I'm aware. For Windows, it should be the WEBSITE_NODE_DEFAULT_VERSION app setting, and for linux, it's the linuxFxVersion site setting.

[htke1]

Hi @satvu I don't understand what you meant by similar issue, but the link which points to azure documentation, yes I have set up the node version correctly.

@hossam-nasr this is screenshot of linuxFxVersion in kudu environment.

[hossam-nasr]

@htke1 I'm not sure where you're getting this view from, so I can't verify. Would you mind following this guide so we can take a closer look?

[htke1]

@hossam-nasr It was from kudu page. (https://XXXXXXX.scm.azurewebsites.net/Env)
And below are the function execution details.

Id=c65e16e4-1f11-4b23-b581-4742fb15cdbd
Time stamp = 2023-07-11 13:09:22.862 |
Region = East Asia

Right now, I have downgrade the function to NODE v14 just for the sake of working it.

[htke1]

Any update regarding this?

[htke1]

@hossam-nasr can you please create a azure function with linux host and set node as 18 then check for kudu node version. It would still show node version as 14.X.X. in kudu console.

[chris-talke-canopi]

Has there been any further traction on this? I can confirm that there is still a Node version mismatch with the linux versions of functions apps when using the remote build pipeline.

func azure functionapp publish <function-app-name> --build remote

By having the following value in a post-install script in the package.json file, you can see the following output:

> node -v

v14.19.2

This issue persists even after applying the linuxFxVersion via the following command:

az functionapp config set --linux-fx-version "node|20" --resource-group "<resource-group-name>" --name "<function-app-name>"