CLion 2016.3 Help

Running and Debugging Node.js

On this page:

Before you start

Install and enable the NodeJS plugin. The plugin is not bundled with CLion, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Local and remote modes of running or debugging Node.js applications

Running a Node.js application in CLion is supported only in the local mode. This means that CLion itself starts the Node.js engine and the target application according to a run configuration and gets full control over the session.

Debugging can be performed in two modes:

  • Locally, with the Node.js engine started from CLion.
  • Remotely, when CLion connects to an already running Node.js application. This approach gives you the possibility to re-start a debugging session without re-starting the Node.js server.
In either case, the debugging session is initiated through a debug configuration

You can also configure the behaviour of the browser and enable debugging the client-side code of the application. This functionality is provided through a JavaScript Debug run configuration, so technically, CLion creates separate run configurations for the server-side and the client-side code, but you specify all your settings in one dedicated NodeJS run configuration.

Running a Node.js application

  1. Create a Node.js run configuration.
  2. To launch the application, select the run configuration from the list on the main tool bar and then choose Run | Run <configuration name> on the main menu or click the Run toolbar button run.png. The Run tool window opens.
  3. Open the browser of your choice and open the page with the URL address generated through the server.listen function based on the port and host parameters. The page shows the result of executing your Node.js application.

Debugging a Node.js application locally

  1. Set the breakpoints in the Node.js code, where necessary. At least one breakpoint is necessary otherwise the program will be just executed. If you want the debugging tool to stop at the first line of your code, set a breakpoint at the first line.
  2. Create a Node.js run/debug configuration.
  3. To start a debugging session, select the required debug configuration from the list on the main tool bar and then choose Run | Debug <configuration name> on the main menu or click the Debug toolbar button debug.png.
  4. Open the browser of your choice and open the starting page of your application. Control over the debugging session returns to CLion.
  5. Switch to CLion, where the controls of the Debug tool window are now enabled. Proceed with the debugging session step through the breakpoints, switch between frames, change values on-the-fly, examine a suspended program, evaluate expressions, and set watches.

Debugging a Node.js application running on a Docker container

  1. Set the breakpoints in the Node.js code, where necessary. At least one breakpoint is necessary otherwise the program will be just executed. If you want the debugging tool to stop at the first line of your code, set a breakpoint at the first line.
  2. On the main menu, choose Run | Edit Configurations. In the Edit Configuration dialog box, that opens, click the Add New Configuration toolbar button add.png, and choose Node.js on the context menu. In the Run/Debug Configuration: Node JS dialog that opens, choose the relevant Node.js interpreter running in a Docker container. Choose one of the existing interpreters from the Node Interpreter drp-down list or configure a new one as described in Configuring Node.js Interpreters.
  3. Specify the Docker container settings. Type the settings manually, or click /help/img/idea/browseButton.png next to the field and specify the settings in the Edit Docker Container Settings dialog that opens, or select the Auto configure check box to have CLion do it automatically.

    To invoke the automatic configuration mode for a Docker container, select the Auto configure check box in the Run/Debug Configuration: Node JS dialog. In the Automatic Configuration mode:

    • CLion creates a new image and installs the npm modules on it.

      To avoid reinstalling the modules on every start of the container and messing up with the local and system-specific dependencies, CLion copies the package.json configuration file to the /tmp/project_modules folder on the image, runs the npm install command, and then copies the modules to the project folder in the container. Changing package.json in the project results in re-building the image.

    • CLion runs the Docker container with the created image and binds your project folder to /opt/project folder in the Docker container to ensure synchronization on update. In addition to that, /opt/project/node_modules will be mapped to the OS temporary directory.

    With automatic configuration, you still need to bind the port that your application is running on with the port of the container. Those exposed ports are available on the Docker host’s IP address (by default 192.168.99.100). Such binding is required when you debug the client side of a Node.js Express application so you need to open the browser from your computer and access the application at the host of the container through the port specified in the application.

    1. Click /help/img/idea/browseButton.png next to the Docker Container Settings field.
    2. In the Edit Docker Container Settings dialog that opens, expand the Port bindings area.
    3. Click /help/img/idea/new.png. The Port bindings dialog box opens. In this dialog box, map the ports as follows:
      • In the Container port text box, type the port specified in your application.
      • In the Host port text box, type the port through which you want to open the application in the browser from your computer.
      • In the Host IP text box, type the IP address of the Docker's host, the default IP is 192.168.99.100. The host is specified in the API URL field on the Docker page of the Settings / Preferences Dialog.
      • Click OK to return to the Edit Docker Container Settings dialog where the new port mapping is added to the list.
    4. Click OK to return to the Run/Debug Configuration: Node JS dialog.

  4. Save the run configuration.
  5. Proceed as as during a local debugging session, as described above.

Node.js multiprocess debugging

CLion supports debugging additional Node.js processes that are launched by the child_process.fork() method or by the cluster module. Such processes are shown as threads in the Frame pane on the Debugger tab of the Debug Tool Window.

  1. Set the breakpoints in the processes to debug.
  2. Create a Node.js run/debug configuration.
  3. Choose the newly created configuration in the Select run/debug configuration drop-down list on the tool bar and click the Debug toolbar button /help/img/idea/debug.png.

    The Debug tool window opens and the Frames drop-down list shows the additional processes as threads as soon as they are launched:

    ws_node_multiprocess.png

    To examine the data (variables, watches, etc.) for a process, select its thread in the list and view its data in the Variables and Debug Tool Window. Watches panes. When you select another process, the contents of the panes are updated accordingly.

See Also

Last modified: 22 November 2016