You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current node 20 version being used by Azure Functions (20.5.1) is causing some unusual behavior when I make http requests that makes the entire Node 20 version of Azure Functions unusable to my application. 20.5.1 is over two months old at this point, and newer versions of node (20.9.0, specifically) resolve the behavior for me. I notice that the Node 18 image is also stuck on the version from August 2023.
WEBSITE_NODE_DEFAULT_VERSION was investigated as a possible workaround, but is not available to me as I am using a Linux-powered function. Currently, I've rolled my function back to using the Node 18 image, as it does not have the defect I see in 20.5.1.
Additional context
I notice that the linux containers are powered by nodesource. This nodesource issue also seems to be demonstrating similar versions as the ones I find in Azure Functions.
The text was updated successfully, but these errors were encountered:
The current node 20 version being used by Azure Functions (20.5.1) is causing some unusual behavior when I make http requests that makes the entire Node 20 version of Azure Functions unusable to my application. 20.5.1 is over two months old at this point, and newer versions of node (20.9.0, specifically) resolve the behavior for me. I notice that the Node 18 image is also stuck on the version from August 2023.
WEBSITE_NODE_DEFAULT_VERSION was investigated as a possible workaround, but is not available to me as I am using a Linux-powered function. Currently, I've rolled my function back to using the Node 18 image, as it does not have the defect I see in 20.5.1.
Additional context
I notice that the linux containers are powered by nodesource. This nodesource issue also seems to be demonstrating similar versions as the ones I find in Azure Functions.
The text was updated successfully, but these errors were encountered: