Adjust the App Service Application settings. Open Azure Portal, go to App Service -> Configuration -> General settings -> Platform settings. Switch your App Service to use 64-bit.If you'd still want to try it out you need to tweak your App Service a bit: In another GitHub issue Marie Hoeger describes the official way to achieve our goal. Buried in one of this GitHub issues Marie Hoeger mentioned that they now have one Node.js version (10.15.2) deployed on the App Services, although it seems this is more for internal testing and she is a bit vague about the support state. Azure App ServiceĪ bit of Googling showed multiple GitHub issues and UserVoice requests to have Node.js 64-bit in a 64-bit App Service and Function Apps etc., going back 3 years even. So I decided to see if things had changed over the past few months. Even if the App Service would be configured to run 64-bit, it would still use a Node.js 32-bit install and no 64-bit installs were provided out of the box. When I was setting up this blog, I already investigated switching to Node.js 64-bit in my Azure App Service but this wasn't supported at the time. Normally, this doesn't really pose an issue, but in some cases (when using packages that get natively build with node-gyp and N-API for example) an application built on 64-bit doesn't run on a 32-bit Node.js binary. Azure DevOps uses a 64-bit Node.js to build my blog, but it gets deployed to an Azure App Service that runs 32-bit Node.js. The Azure DevOps pipeline for this blog broke yesterday, and during investigation I noticed something strange. Seeing a post by Jessica Deen triggered me to update this post. Updated : there is now an official way to have 64-bit Node.js on your Windows-based App Service in Azure.
0 Comments
Leave a Reply. |