Dart Command Line Application-specific configuration settings

Item

Description

Name

In this text box, specify the name of the run/debug configuration.

Share

Select this check box to make the run/debug configuration available to other team members.

If the directory-based project format is used,
the settings for a run/debug configuration are stored in a separate .xml file in the .idea\runConfigurations folder
if the run/debug configuration is shared, or in the .idea\workspace.xml file otherwise.

If the file-based format is used,
the settings are stored in the .ipr file for shared configurations, or
in the .iws file otherwise.

This check box is not available when editing the run/debug configuration defaults.

Dart file

In this text box, specify the Dart file to start the application from. The file must contain a main() method.
Type the path to the file manually or click the Browse button and select the file in the dialog box that opens.

VM options

In this text box, specify the options to launch the Dart Virtual Machine with.

If an option includes spaces,
enclose the spaces or the argument that contains the spaces in double quotes,
for example,
some" "arg or "some arg".

If an option includes double quotes (e.g. as part of the argument),
escape the double quotes by means of the backslashes,
for example,
-Dmy.prop=\"quoted_value\".

Program arguments

In this text box, type the list of arguments to start the application with. Use the same format as for VM options.

Environment Variables

In this field, specify the environment variables for the NodeJS executable file, if applicable.
Click the Browse button 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 and specify the variable name and value.

To discard a variable definition, select it in the list and click the Delete toolbar button .

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.

Working Directory

In this field,
specify the working directory of the application.
All references in the starting Dart application file, for example, imports,
will be resolved relative to this folder, unless such references use full paths.

By default, the field shows the project root folder. To change this predefined setting,
choose the desired folder from the drop-down list, or type the path manually, or click the Browse button
and select the location in the dialog box, that opens.

Toolbar

Item

Shortcut

Description

Alt+Insert

Click this button to add a new configuration to the list.

Alt+Delete

Click this button to remove the selected configuration from the list.

Ctrl+D

Click this button to create a copy of the selected configuration.

Edit defaults

Click this button to edit the default configuration templates.
The defaults are used for newly created configurations.

or

Alt+Up or Alt+Down

Use these buttons to move the selected configuration or folder up and down in the list.

The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.

If one or more run/debug configurations are in focus, the selected run/debug configurations
are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.

Move run/debug configurations to a folder using drag-and-drop, or the buttons.

Sort configurations

Click this button to sort configurations in alphabetical order.

Common options

Item

Description

Name

In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.

Defaults

This node in the left-hand pane of the dialog box contains the default run/debug configuration settings.
Select the desired configuration to change its default settings in the right-hand pane.
The defaults are applied to all newly created run/debug configurations.

Share

Select this check box to make the run/debug configuration available to other team members.

If the directory-based project format is used,
the settings for a run/debug configuration are stored in a separate .xml file in the .idea\runConfigurations folder
if the run/debug configuration is shared, or in the .idea\workspace.xml file otherwise.

If the file-based format is used,
the settings are stored in the .ipr file for shared configurations, or
in the .iws file otherwise.

This check box is not available when editing the run/debug configuration defaults.

Single instance only

If this check box is selected, this run/debug configuration cannot be launched more than once.

Every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances
of the same run/debug configuration, and displays a confirmation dialog box. If you click OK
in the confirmation dialog box, the first instance of the runner will be stopped,
and the next one will take its place.

This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug
configurations of the same type consumes too much of the CPU and memory resources.

If this check box is not selected, it is possible to launch as many instances of the runner as required.
So doing, each runner will start in its own tab of the Run tool window.

Before launch

Specify which tasks must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.

Item

Keyboard shortcut

Description

Alt+Insert

Click this icon to add a task to the list. Select the task to be added:

Run External tool.
Select this option to run an application which is external to IntelliJ IDEA.
In the dialog that opens, select the application or applications that should be run.
If the necessary application is not defined in IntelliJ IDEA yet, add its definition.
For more information, see Configuring Third-Party Tools and External Tools.

Build Artifacts.
Select this option to have an artifact or artifacts built.
In the dialog that opens, select the artifact or artifacts that should be built.

Run Another Configuration.
Select this option to have another run/debug configuration executed.
In the dialog that opens, select the configuration to run.

This option is available only if you have already at least one run/debug configuration in the current project.

Run Ant target.
Select this option to have an Ant target run.
In the dialog that opens, select the target to be run.
For more information, see Ant.

Run Grunt task. Select this option to run a Grunt task.
In the Grunt task dialog box that opens, specify the Gruntfile.js where the required task is defined,
select the task to execute,
and specify the arguments to pass to the Grunt tool.

Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.

Run Gulp task. Select this option to run a Grunt task.
In the Gulp task dialog box that opens, specify the Gulpfile.js where the required task is defined,
select the task to execute,
and specify the arguments to pass to the Gulp tool.

Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.

Run npm Script. Select this check box to execute an npm script.
In the NPM Script dialog box that opens, specify the package.json file where the required script is defined,
select the script to execute, choose the command to apply to it, and specify the arguments to execute the script with.

Specify the location of the Node.js interpreter and the parameters to pass to it.

Compile TypeScript. Select this option to run the built-in TypeScript compiler
and thus make sure that
all the changes you made to your TypeScript code are reflected in the generated JavaScript files.
In the TypeScript Compile Settings dialog that opens, select or clear the Check errors check box
to configure the behaviour of the compiler in case any errors are detected:

If the Check errors check box is selected, the compiler will show all the errors
and the run configuration will not start.

If the Check errors check box is cleared, the compiler will show all the detected errors
but the run configuration still will be launched.

Generate CoffeeScript Source Maps.
Select this option to have the source maps for your CoffeeScript sources generated.
In the dialog that opens, specify where your CoffeeScript source files are located.
For more information, see CoffeeScript Support.

Run Maven Goal.
Select this option to have a Maven goal run.
In the dialog that opens, select the goal to be run.