Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for more recent node versions #999

Open
GravlLift opened this issue Nov 15, 2023 · 0 comments
Open

Support for more recent node versions #999

GravlLift opened this issue Nov 15, 2023 · 0 comments

Comments

@GravlLift
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant