5/13/2023 0 Comments Windows update node versionIf you develop and test functions locally, make sure to update Azure Functions Core Tools to the latest version as well. If you find out the Node.js version you're aiming for is not supported, you will need to upgrade the Functions runtime. There was a platform upgrade for Azure Functions v2, where this app setting could remain at ~2 while in reality the runtime became 3.x. Note FUNCTIONS_EXTENSION_VERSION application setting (e.g. In the returned JSON, you will find the "version" property. Get your function app's master key and make a request: curl. Here is the most reliable way to check the runtime version that I found. How to find out Azure Functions runtime version you use? You can see runtime versions and their supported Node.js versions here. Node.js versions that are available to you depend on the OS and the Functions Runtime version used. Azure Functions Runtime version #īefore we get to Node.js versions, there's an important concept of Azure Functions Runtime version. I've tested all combinations of Linux/Windows, Consumption/Premium to verify the process of changing Node.js versions. How to make the change with Azure Portal, CLI, ARM, Terraform?. Is there any difference when running in Consumption and Premium hosting plans?.How to change/upgrade Node.js version for Linux and Windows function apps?.How do you know which Node.js version is currently used?.You may want to upgrade when it reaches the GA status. You may consider upgrading to benefit from new features, performance improvements and security fixes.Īs we're approaching March 2021, Node.js 12 is the recommended version in Azure Functions and version 14 is in preview. If you haven't touched your function app for a while there's a chance it's running an older version of Node.js.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |