Run | Edit Configurations || Attach to Node.js/Chrome
Discover great apps, games, extensions and themes for Google Chrome. WebStorm should one day accept json definitions directly to enable autocomplete for the functions defined. Meanwhile, you can use the program at to convert the json files to js to enable auto-complete for the chrome extension APIs.
This page provides descriptions of the configuration-specific items as well as options that are common for all run/debug configurations. To learn how to use this configuration, see Debugging a running Node.js application.
In this dialog, create configurations for debugging already running Node.js applications. This approach gives you the possibility to re-start a debugging session without re-starting the Node.js server.
Also use this configuration to debug background and additional main processes of NW.js applications, see Run/Debug Configuration: NW.js.
Before you start
Download and install Node.js.
Specific Attach to Node.js/Chrome configuration settings
Item | Description |
---|---|
Host | In this field, specify the host where the application is running. Capture one black friday sale. |
Port | In this field, specify the port passed to --inspect , --inspect-brk , or --debug when starting the Node.js process to connect to. Copy this port number from the information message in the Run tool window that controls the running application. |
Attach to | In this area, choose the debugging protocol to use:
|
Reconnect automatically | Select this checkbox to enable the WebStorm built-in debugger to re-attach to a running Node.js process after the code of the application is changed. This lets you debug Node.js applications that use the nodemon utility, which automatically reloads your Node.js process when the code is updated. See Debugging an application that uses nodemon for details. |
Remote URLs of local files | In this area, specify the remote paths for the project folders. This is helpful if the root folder of the running application is different from the name of you WebStorm project root folder. In the example below, the WebStorm project root folder /Users/WsProjects/express is mapped to /usr/src/app on the server. |
Jetbrains Ide Support Chrome
Common
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Chrome Webstorm Plugin
Item | Description |
---|---|
Name | Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10. |
Store as project file | Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project. Logitech g hub for mac. Download Logitech G HUB for Mac - All-purpose application designed to help you control all your Logitech peripherals, manage profiles, lighting effects, and bindings, as well as synchronize. Logitech G HUB Software lets you customize Logitech G gaming mice, keyboards, headsets, speakers, and other devices. Logitech G HUB Advanced Gaming Software, RGB & Game Profiles. Created with Snap. Created with Snap. TOTAL GEAR CONTROL. Download for WINDOWS DOWNLOAD FOR Mac OS. CREATE GAME PROFILES DOWNLOAD AND SHARE WITH THE COMMUNITY. CONTROL YOUR STREAM BUILT IN OBS AND THIRD PARTY APP INTEGRATION. By default, it is disabled, and WebStorm stores run configuration settings in .idea/workspace.xml. |
Toolbar
Chrome Web Store Extensions
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Create a run/debug configuration. | |
Alt+Delete | Delete the selected run/debug configuration. Note that you cannot delete default configurations. | |
Ctrl+D | Create a copy of the selected run/debug configuration. Note that you create copies of default configurations. | |
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent. | ||
View and edit the template (that is, the default run/debug configuration settings). The templates are displayed under the Templates node and used for newly created configurations. | ||
/ | Alt+Up/ Alt+Down | Move the selected run/debug configuration up and down in the list. The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration. Default templates of run/debug configurations are always sorted alphabetically. |
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders. To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created. Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons. To remove grouping, select a folder and click . | ||
Click this button to sort configurations in the alphabetical order. |
Before Launch
In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Click this icon to add one of the following available tasks:
| |
Alt+Delete | Click this icon to remove the selected task from the list. | |
Enter | Click this icon to edit the selected task. Make the necessary changes in the dialog that opens. | |
/ | Alt+Up/ Alt+Down | Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list. |
Show this page | Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration. | |
Activate tool window | By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5. |