Run Grunt task: select this option to run a Grunt task. Run File Watchers: select this option to have CLion apply all the currently active File Watchers. In the dialog that opens, select the configuration to be run. Run Another Configuration: select to execute another run/debug configuration. For more information, see External tools and External Tools. If it is not defined in CLion yet, add its definition. In the dialog that opens, select one or multiple applications you want to run. Run External tool: select to run an external application. The tasks are performed in the order they appear in the list.Ĭlick this icon to add one of the following available tasks: In this area, you can specify tasks to be performed before starting the selected run/debug configuration. Ĭlick this button to sort configurations in the alphabetical order. To remove grouping, select a folder and click. Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons. If only a category is in focus, an empty folder is created. To create a folder, select the configurations within a category, click, and specify the folder name. You can group run/debug configurations by placing them into folders. Move into new folder / Create new folder. Click this button to save a temporary configuration as permanent. The button is displayed only when you select a temporary configuration. Note that you create copies of default configurations. Note that you cannot delete default configurations.Ĭreate a copy of the selected run/debug configuration. When you edit a run configuration (but not a run configuration template), you can specify the following options:ĭelete the selected run/debug configuration. Click in the Test name field and configure a list of tests to run using the and buttons. Test: choose this option to run individual tests from a test file and specify the path to this file in the Test file field. Click in the Suite name field and configure a list of suites to run using the and buttons. Suite: choose this option to run individual suites from a test file and specify the path to this file in the Test file field. Test file: choose this option to run only the tests from one file and specify the path to this file in the Test file field. With the default configuration, tests are recognized by the default value of the testRegex property. The available options are:Īll tests: choose this option to run all the tests from the nfig configuration file or from the generated Jest default configuration. In this area, specify the tests to be executed. In this field, optionally specify the environment variables for executing commands. As a result, any test in the current run configuration restarts automatically on changing the related source code, without clicking the Rerun button. For example, add a -watch flag to turn on the autotest-like runner. In this field, type the Jest CLI options to be passed to Jest. To change this predefined setting, specify the path to the desired folder or choose a previously used folder from the list. By default, the Working directory field shows the project root folder. In this field, specify the working directory of the application. In this field, specify the location of the jest, react-scripts, react-script-ts, react-super-scripts, or react-awesome-scripts package. Otherwise, by default the debug process will use V8 Debugging Protocol. Use -inspect or -inspect-brk parameter when you are using Node.js v7 for Chrome Debugging Protocol support.
CLION RUN CONFIGURATION INSTALL
Therefore make sure you have the coffeescript package installed locally as described in Install the CoffeeScript compiler. This mode requires that the register.js file, which is a part of the coffeescript package, is located inside your project. Use -require coffeescript/register to have CoffeeScript files compiled into JavaScript on the fly during run. In this field, type the Node.js-specific command-line options to be passed to the Node.js executable file. You can also choose another configured local interpreter or click and configure a new one. In most cases, CLion detects the project default interpreter and fills in the field itself. If you choose the Project alias, CLion will automatically use the project default interpreter from the Node interpreter field on the Node.js and NPM page. In this field, specify the Node.js interpreter to use. If no appropriate package.json file is found, then a Jest default configuration is generated on the fly. The search is performed in the file system upwards from the working directory. If the field is empty, CLion looks for a package.json file with a jest key. In this field, optionally specify the nfig file to use: select the relevant file from the list, or click and select it in the dialog that opens, or just type the path in the field.
0 kommentar(er)
