Run/Debug Configuration: Node.js
In this dialog box, create configurations for running and debugging Node.js applications locally. "Locally" in the current context means that AppCode itself starts Node.js installed on your computer, whereupon initiates a running or debugging session.
Getting access to the Run/Debug Configuration: Node.js dialog
|Node interpreter||In this field, specify the Node.js interpreter to use. This can be a local or remote Node.js interpreter or a Node.js on Windows Subsystem for Linux. Select an interpreter from the list or click and configure a new one in the dialog that opens.|
|Node parameters|| In this text box, type the Node.js-specific command line options to be passed to the NodeJS executable file. The most common options are: |
|Working directory||In this field, specify the working directory of the application. By default, the field shows the project root folder.|
|Environment variables|| In this field, specify the environment variables for the Node.js executable file, if applicable. Click Browse to the right of the field and configure a list of variables in the Environment Variables dialog box, that opens: |
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are:
|Docker container settings||In this field, type the settings manually, or click next to the field and specify the settings in the Edit Docker Container Settings dialog that opens, or select the Auto configure checkbox to have AppCode do it automatically.|
|Auto configuration|| Select this checkbox to have AppCode configure the container settings. In the Automatic configuration mode: |
Even with automatic configuration, you still need to bind the port on which your application is running 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. In this case, you need to open the browser from your computer and access the application at the container host through the port specified in the application.
To configure port bindings
Browser / Live Edit tab
In this tab, configure the behaviour of the browser and enable debugging the client-side code of the application. This functionality is provided through a
|Open browser||In the text box in this area, specify the URL address to open the application at. If you select the After Launch check box, the browser will open this page automatically after the application starts. Alternatively you can view the same result by opening the page with this URL address in the browser of your choice manually.|
|After launch|| Select this check box Choose the browser to use from the drop-down list next to the After launch checkbox. |
V8 Profiling tab
|Record CPU profiling info|| Select this checkbox to start logging the CPU profiling data when the application is launched. The controls in the area below become enabled. Specify the following: |
|Allow taking heap snapshots|| Select this checkbox if you are going to run memory profiling. The controls in the area below become enabled. Specify the following: |
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
|Name||In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example. from the Run popup (⌃⌥R).|
|Share|| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
|Single instance only|
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
|⌘N||Create a run/debug configuration.|
|⌘⌦||Delete the selected run/debug configuration. Note that you cannot delete default configurations.|
|⌘D||Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.|
|Edit Templates||View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.|
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
|Move into new folder / Create new folder|| |
You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag-and-drop or and buttons.
To remove grouping, select a folder and click .
|Sort configurations||Click this button to sort configurations in the alphabetical order.|
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
|Configurations available in Run Dashboard|| |
In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the configuration types for which you have created one ore more configurations.
|Confirm rerun with process termination||The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration. |
|Temporary configurations limit||Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
Before Launch options
In this area you can specify tasks that must be be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
|⌘N|| Click this icon to add one of the following available tasks: |
|⌘⌦||Click this icon to remove the selected task from the list.|
|⏎||Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.|
|/||⌃↑/⌃↓||Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)|
|Show this page||Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Activate tool window|| |
Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing ⌘4 or ⌘5.