The good thing is development of many Azure things happens in the open! A bit of searching revealed a pull request containing the required magic, and let me to discovering the one thing needed to get the Azure side of things set up: starting our app with the -inspect flag. Unfortunately, that did not work for me… At time of writing (see this post’s publish date), debugging Node.js on App Service on Linux is still in preview and my guess is not all regions have the required magic deployed. On the Azure side, there is only one thing that has to happen: our Node.js application has to run with node’s -inspect flag.Īnd great news! As described in a post by Kenneth Auchenberg, things should “just work ™”!
Other thing we will need, of course, are an active Azure subscription, as well as an App Service on Linux that we can play with.
WEBSTORM NODEJS UPDATE
(or az extension update -name webapp if already installed) To get it, open a command prompt, make sure the az command is on the PATH, and run: The latest version of the Azure CLI 2.0.Sweet! But… how? The blog post did not mention a lot of details on the debugging part, so let’s walk through it, shall we? Remote debugging of Node.js apps on Azure App Service from WebStorm! Prerequisitesįirst of all, we will need a number of things on our machine: Remote debugging, in public preview: You can now choose to remote debug your Node.JS applications running on App Service on Linux.
One that I was interested in was this one: Remote debugging of Node.js apps on Azure App Service from WebStorm Edit on GitHubĪt Microsoft Build 2018, a number of Azure App Service on Linux enhancements were announced.
0 kommentar(er)
