RubyMine 5.4.0 Web Help

4.0+

To get access to this dialog box:

  1. Download and install the NodeJS framework.

In this dialog box, create configurations for running and debugging of nodeJS applications locally. "Locally" in the current context means that RubyMine itself starts the NodeJS framework installed on your computer, whereupon initiates a running or debugging session.

This section provides descriptions of the configuration-specific items, as well as the toolbar and options that are common for all run/debug configurations.

ItemDescription
Path to Node In this field, specify the NodeJS installation home. Type the path to the NodeJS executable file manually, or click the Browse button browseButton.png and select the location in the dialog box, that opens.

If you have appointed one of the installations as default, the field displays the path to its executable file.

Node parameters In this text box, type the NodeJS-specific command line options to be passed to the NodeJS executable file. The acceptable options are:
--debug==<port for connect to debugger remotely> Specify this option to enable remote debugging of the application without re-starting the NodeJS server.
-v, --version Print the current version of NodeJS.
-e, --eval script Evaluate script.
--v8-options Print v8 command line options.
--vars Print various compiled-in variables.
--max-stack-size=val Set max v8 stack size (bytes).
Path to Node App JS file In this field, specify the full path to the NodeJS file to start running or debugging from.

If you are going to debug CoffeeScript, specify the path to the generated JavaScript file with source maps. The file can be generate4d externally or through transpilation using file watchers. For more details, see Transpiling CoffeeScript to JavaScript.

Application parameters In this text box, type the NodeJS-specific arguments to be passed to the starting NodeJS application file through the process.argv array.
Working directory In this field, specify the location of the files referenced from the starting NodeJS application file, for example, includes. If this file does not reference any other files, just leave the field empty. Choose the folder from the drop-down list, or type the path manually, or click the Browse button browseButton.png and select the location in the dialog box, that opens.
Environment variables In this field, specify the environment variables for the NodeJS executable file, if applicable. Click the Browse button browseButton.png to the right of the field and configure a list of variables in the Environment Variables dialog box, that opens:
  • To define a new variable, click the Add toolbar button add.png and specify the variable name and value.
  • To discard a variable definition, select it in the list and click the Delete toolbar button delete.png.
  • Click OK, when ready

The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are:

NODE_PATH A :-separated list of directories prefixed to the module search path.
NODE_MODULE_CONTEXTS Set to 1 to load modules in their own global contexts.
NODE_DISABLE_COLORS Set to 1 to disable colors in the REPL.
Run with CoffeeScript pluginIf this check box is selected, you can launch the CoffeeScript files directly, without previously transpiling them to JavaScript.
Path to coffee executableSpecify here the path to the executable file that launches the CoffeeScript transpiler.
CoffeeScript parametersSpecify here the parameters to be passed to CoffeeScript.

See Also

Concepts:

Procedures:

Reference:

Web Resources:

JavaScript Support: