Specify a name for the run configuration to quickly identify it among others when editing or running.Īllow running multiple instances of this run configuration in parallel.īy default, it is disabled, and when you start this configuration while another instance is still running, WebStorm suggests stopping the running instance and starting another one. When you edit a run configuration (but not a run configuration template), you can specify the following options: This field only appears when a remote interpreter via Docker Compose is selected. Learn more from the Docker official website. Accept the default settings or click and specify custom ones, for example, custom Docker Compose flags, like -rm or -service-ports. In this area, specify the commands and options to be passed to Docker Compose. This field only appears when a Docker-based remote interpreter is selected. This read-only field shows port and volume bindings. NODE_DISABLE_COLORS: Set to 1 to disable colors in the REPL. NODE_MODULE_CONTEXTS: Set to 1 to load modules in their own global contexts. NODE_PATH: A :-separated list of directories prefixed to the module search path. The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators, for example: To discard a variable definition, select it in the list and click. To define a new variable, click and specify the variable name and value. Click Browse to the right of the field and configure a list of variables in the Environment Variables dialog, that opens: In this field, specify the environment variables for the Node.js executable file, if applicable. You can also choose the relevant package alias ( npm or yarn) or specify an explicit path to a custom installation of a package manager. If you choose the Project alias, WebStorm will use the default project package manager from the Node.js page. 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. Webstorm node debugger 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. Webstorm node debugger windows#See Configuring remote Node.js interpreters, Configuring a local Node.js interpreter, and Using Node.js on Windows Subsystem for Linux for details. You can also choose another configured local or remote interpreter or click and configure a new one. In most cases, WebStorm detects the project default interpreter and fills in the field itself. If you choose the Project alias, WebStorm will automatically use the project default interpreter from the Node interpreter field on the Node.js page. In this field, specify the Node.js interpreter to use. Learn more from the npm official website. In this field, specify the command-line arguments to execute a script with. The list contains all the scripts defined within the scripts property in the package.json file. Learn more at npm documentation, under the section CLI Commands.įrom this drop-down list, choose the script to which the chosen command will be applied. Choose the file from the drop-down list which shows all the package.json files detected in the current project or click and choose the required package.json in the dialog box that opens.įrom this list, choose the npm CLI command to execute, by default run-script is selected. In this field, specify the package.json file to run the scripts from.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |