Stand-up (Part 4): Debug your node.js application

This is the fourth blog post in our series around developing a node.js application using Monaco. In this part you will learn how to debug your node.js applications using node-inspector.

If you are interested in other parts of this series, please use the links below:

  1. Part 1: Introduction
  2. Part 2: How to configure the workspace for IntelliSense
  3. Part 3: Using Mocha for server side unit testing
  4. Part 4: How to debug node.js applications on Azure
  5. Part 5: How to connect to an existing workspace using source control
  6. Part 6: Best practices leveraging development and production sites

How to enable node-inspector for debugging

Thankfully, all Azure web sites come with node inspector pre-installed. This tool is the standard when it comes to debugging node.js applications. It is very easy to setup on Azure.

Open our web.config and find the <iisnode> element to add the following attribute:


Then restart the application (Ctrl+F5) and open the following URL in your browser: http://<sitename> (if your Azure web site is called “monacotesting”, the resulting URL would be If you take a look into the web.config file you will notice some rewriting rules. One of them is responsible to support node inspector. The web.config file is automatically generated for you once you run your application out of Monaco. The <iisnode> element can be used to configure some interesting development settings. You can read about all the available options here.

You will find yourself inside node-inspector and you can start adding a breakpoint and debugging your express application. Once you are done debugging, it is recommended to change the configuration in web.config back to “false”. You can also navigate to http://<sitename> This will terminate the debugger and debugee processes in Azure.

Note that node-inspector is known to work best in Chrome as browser.

If you are interested in a video with step by step instructions for enabling debugging in Monaco, you can also check out our video on Channel9 on this topic.


In this part of the series you have learned how to enable node-inspector from Monaco to debug your node.js application. Stay tuned for the next part where you will learn how to use source control with Monaco and work with development and production web sites.


Comments (2)

  1. OutCust says:

    Hi, may be you can help me, i'm run debug mode, but loaded only node files, also i have the error

    (WebSocket connection to 'ws://' failed: Error during WebSocket handshake: Unexpected response code: 404)

    web.config ( <webSocket enabled="true" />) and

    site settings : websocket – enabled…/debug

  2. ryan says:

    Hi, is there a way to make the variable inspector go deeper?  Right now when I look at an object, if that object contains another object, I cannot look at that object.

Skip to main content