Run/Debug Configuration: Meteor
Use this dialog box to create configurations for running and debugging Meteor applications.
The dialog box is available when the Meteor plugin is enabled. The plugin is bundled with WebStorm and activated by default. If the plugin is not activated, enable it on the Plugins page of the Settings / Preferences Dialog as described in Enabling and Disabling Plugins.
On this page:
Configuration Tab
Item | Description |
---|---|
Name | In this text box, specify the name of the current run/debug configuration. |
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. |
Meteor Executable | In this field, specify the location of the Meteor executable file (see Installing Meteor). |
Program Arguments |
In this field,
specify the command line additional parameters to be passed to the executable file on start up, if applicable.
These can be, for example, --dev , --test , or --prod to indicate the environment in which the application is running (development, test,
or production environments) so different resources are loaded on start up.
|
Working Directory |
In this field,
specify the folder under which the application files to run are stored.
This folder must contain a .meteor folder in the root to be treated a Meteor project.
By default, the field shows the path to the WebStorm project root.
Technically, several Meteor projects that implement different applications can be combined within one single WebStorm project.
To run and debug these applications independently, create a separate run configuration for each of them
with the relevant working directory.
To avoid port conflicts, these run configurations should use different ports. In the Program Arguments field,
specify a separate port for each run configuration in the format |
Environment Variables | In this field, specify the environment variables for the Meteor executable file, if applicable. |
Browser / Live Edit Tab
In this tab,
configure the behaviour of the browser and enable debugging the client-side code of the application. This functionality is provided through a JavaScript Debug
run configuration, so
technically, WebStorm creates separate run configurations for the server-side and the client-side code,
but you specify all your settings in one dedicated Meteor run configuration.
Item | Description |
---|---|
Open Browser | In the text box in this area, specify the URL address to open the application at. If you select the After Launch check box, the browser will open this page automatically after the application starts. Alternatively you can view the same result by opening the page with this URL address in the browser of your choice manually. |
After Launch |
Select this check box
to have a browser started automatically after a debugging session is launched. Specify the browser to use in the drop-down list next to the check box.
|
With JavaScript Debugger | Select this check box to enable debugging the client-side code in the selected browser. |
Toolbar
Common options
Item | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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, WebStorm 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. | ||||||||||||||||||||||||
Before launch | 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.
|