WebStorm 2024.2 Help

Run applications

With WebStorm, you can run entire applications, single scripts, or tests right from the editor, using the context menu or gutter icons. If you need to pass some parameters to your application or launch a tool, for example, an npm script, before running, create a language- or framework-specific Run/Debug Configuration and invoke it.

All the run configurations that are currently available in a project are shown in the Select Run/Debug Configuration list.

Learn more from Run/debug configurations.

If you want to see the list of all currently running applications, select Run | Show Running List from the main menu. For more information, refer to Show running processes.

After a run session starts, the icon in the Run tool window and in the Run/Debug Configuration Selector toggles to active_run_icon.png.

Quick way

Run from the editor

If you are not going to pass any parameters to your program, and your program does not require any specific actions to be performed before start, you can run it right from the editor.

  • To run client-side JavaScript code in the browser, open the HTML page that references it.

    WebStorm has a built-in web server that can be used to preview and debug your application in a web browser or IDE's built-in browser. This server is always running and does not require any manual configuration.

    1. In the editor, open the HTML file with the JavaScript reference, hover over the code to show the browser icons bar: the WebStorm icon Chrome Firefox Safari Opera Internet Explorer Edge, and then click the icon that indicates the desired browser. See Preview output of HTML files.

    2. Alternatively:

      Open the HTML file with the JavaScript reference in the editor or select it in the Project tool window, and then select Run <HTML file name> from the context menu.

      Run client JavaScript

      WebStorm creates a temporary run/debug configuration of the type JavaScript Debug which you can later save, refer to Saving a temporary configuration as permanent.

  • To run a script, open it in the editor or select it in the Project tool window, and then select Run <script file name> from the context menu.

    Run script

    WebStorm creates a temporary run/debug configuration of the type Node.js.

  • To run a test, click the gutter icon next to it or press Ctrl+Shift+F10. The gutter icon changes depending on the state of your test, refer to Performing tests and framework-specific pages under Testing JavaScript.

    Run single test from the editor
  • To run an npm, Yarn, or pnpm script:

    1. Open package.json, click Run in the gutter next to the script, and choose Run <script_name>, refer to Running and debugging scripts from package.json.

    2. Alternatively:

      Use the npm tool window.

    Learn more from Running and debugging scripts.

Run the current file

You can run single files using a dedicated option on the toolbar. The run and debug buttons are active and allow you to instantly run the currently opened file.

  1. In the editor, open the file that you want to run.

  2. Click Run next to the Current File option on the toolbar.

    Running a single file from the toolbar

You can access other runners as well: expand the list and select Current File. From the widget that opens, you can debug the code, run it with coverage, or open the run configuration to specify more options.

More options for running current file

Customizable way

Use a run/debug configuration

If you are going to pass parameters to your program, add VM options (for example, to allow remote debugging), or otherwise customize the startup of your program, use a run/debug configuration.

Edit and save a temporary configuration, or create a new run/debug configuration from a template and use one of the following options to run it:

  • Click Run from the Run/Debug Configurations dialog.

    Run/debug configuration: the Run button
  • Select the configuration from the toolbar switcher and click The Run button or press Shift+F10.

    Run configuration selector
  • Press Alt+Shift+F10 and select the configuration on the pop-up window that opens.

When the application starts, you can view its output and interact with it in the Run tool window. Every run/debug configuration creates a separate tab when you run it.

Tabs in the Run tool window

For more information about tool windows and how to manage them, see the Tool windows topic.

Re-run applications

  • On the toolbar of the Run tool window, click the Rerun button or press Shift+F10.

    Re-run button

Stop and pause applications

When you stop a program, its process is interrupted and exits immediately. When you pause a program, it continues running in the background, but its output is suspended.

Stop a program

  • In the Run tool window, click the Stop button on the toolbar. Alternatively, press Ctrl+F2 and select the process to stop.

Pause the program output

  • Right-click in the Run tool window and select Pause Output from the context menu. Use the same toggle to resume the program.

    Pause output

Show running processes

You can view the list of all active run or debug sessions and navigate between them.

  • Go to Run | Show Running List. In the top-right corner of the editor, WebStorm shows a list with all active applications.

CPU and Memory Live Charts

WebStorm provides a way to monitor live performance statistics for a running process through CPU and Memory Live Charts.

As opposed to viewing static figures, live data may help you to visualize resource consumption, identify resource-related bottlenecks, and understand how certain events affect the program performance.

For example, in the picture below, we can see what a memory leak looks like in the Heap Memory chart. Sometimes it is enough to figure out the cause, and when it is not enough, it can give a clue for further investigation.

Memory leak on CPU and Memory Live Charts

CPU and Memory Live Charts are automatically shown for all programs that you run from WebStorm:

CPU and Memory Live Charts in the Run tool window

For more information, refer to Monitor resources usage.

Last modified: 28 June 2024