Run/Debug Configuration: Grunt.js
In this dialog box, create configurations for running Grunt.js tasks.
On this page:
- Getting access to the Run/Debug Configuration: Grunt dialog
- Grunt-specific configuration settings
- Common options
Getting access to the Run/Debug Configuration: Grunt dialog
- Install and enable the Node.js plugin. The plugin is not bundled with AppCode, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
- Download and install the Node.js runtime environment that contains the Node Package Manager(npm).
- Install Grunt.
Grunt-specific configuration settings
|Gruntfile|| In this field, specify the location of the |
|Tasks|| In this field, specify the tasks to run. Do one of the following: |
|Force execution||Select this checkbox to have Grunt ignore warnings and continue executing the launched task until the task is completed successfully or an error occurs, If the checkbox is cleared, the task execution is stopped by the first reported warning.|
|Verbose mode||Select this checkbox to have the verbose mode applied and thus have a full detailed log of a task execution displayed.|
|Node Interpreter|| In this field, specify the Node.js interpreter to use. Choose one of the configured interpreters or click and configure a new one.|
If you have appointed one of the installations as default, the field displays the path to its executable file.
|Node Options||In this text box, type the Node.js-specific command line options to be passed to the Node.js executable file. See Node Parameters for details.|
|Grunt-cli Package|| In this field, specify the path to the globally installed |
|Environment Variables|| In this field, specify the environment variables for the Node.js 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: |
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are:
|⌘N||Click this button to add a new configuration to the list.|
|⌘⌦||Click this button to remove the selected configuration from the list.|
|⌘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||⌃↑ or ⌃↓||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.
|Move into new folder / Create new folder||Use this button to create a new folder. |
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.|
|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. |
The shared run/debug configurations are kept in separate xml files under
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, AppCode 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.
|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. |