Using Gulp Task Runner
GoLand integrates with the Gulp.js Task Runner. GoLand parses Gulpfile.js files, recognizing definitions of tasks, shows tasks in a tree view, lets you navigate between a task in the tree and its definition in the Gulpfile.js file, and supports running and debugging tasks.
Gulp.js tasks can be run from the tasks tree in the dedicated Gulp Tool Window, or from the Gulpfile.js file, by launching a Gulp.js run configuration, or as aa before-launch task from another run configuration. GoLand shows the result of executing a task in the Run tool window. The tool window shows the Grunt output, reports the errors occurred, lists the packages or plugins that have not been found, etc. The name of the last executed task is displayed on the title bar of the tool window.
To use Gulp in a GoLand project, you need two packages:
A globally installed gulp-cli package (Gulp command line interface) for executing Gulp commands.
A gulp package installed as a development dependency to build the project tasks tree and provide coding assistance while editing the Gulpfile.js file. Learn more about Gulpfile.js from the Gulp.js official website.
To install gulp-cli globally
To install Gulp.js in a project
Running Gulp.js tasks from the tasks tree
GoLand lets you run Gulp.js tasks easily and fast right from the tasks tree in the Gulp tool window. GoLand automatically creates a temporary run configuration which you can save and use later, if necessary.
Gulp.js starts building a tasks tree as soon as you invoke Gulp.js by choosing Show Gulp Tasks on the context menu of a Gulpfile.js in the Project tool window or of a Gulpfile.js opened in the editor. The tree is built according to the Gulpfile.js file on which Gulp.js was invoked. If you have several Gulpfile.js files in your project, you can build a separate tasks tree for each of them and run tasks without abandoning the previously built tasks trees. Each tree is shown under a separate node.
To open the Gulp tool window
When you build a tree of tasks for the first time during the current GoLand session, the Gulp tool window is not opened yet.
By default GoLand does not recognize ES6 in Gulpfile.js and fails to build a tasks tree. To solve this problem, update the default Gulp.js run configuration.
To build a tasks tree from a ES6 Gulpfile.js
Under the Templates node, click Gulp.js.
In the Run/Debug Configuration: Gulp.js dialog that opens, type
--harmonyin the Node options field and click OK.
To build a tree of tasks from the Gulp tool window
In the Gulp tool window, click on the toolbar and choose the required Gulpfile.js file from the list. By default, GoLand shows the Gulpfile.js file in the root of your project.
If you have another Gulpfile.js file, click Choose Gulpfile.js and select the Gulpfile.js file you need in the dialog that opens. GoLand adds a new node with the path to the chosen Gulpfile.js file on its title and builds a tasks tree under the new node.
To re-build a tree
To sort the tasks in a tree by their names
To run a task
Double-click the task.
Select the task in the tree and press Enter or choose Run <task name> from the context menu.
To run the default task
Select the root node in the tree, and choose Run default from the context menu.
To run several tasks
To navigate to the definition of a task
Running tasks from Gulpfile.js
Position the cursor at the definition of the task to run and choose Run <task name> from the context menu. GoLand creates and launches a temporary run configuration with the name of the selected task.
To save an automatically created temporary run configuration, position the cursor at the definition of the task for which it was created and choose Save <task name> from the context menu of the selection.
Running and debugging tasks according to a run configuration
Besides using temporary run configurations that GoLand creates automatically, you can create and launch your own Gulp.js run configurations.
To create a Gulp.js run configuration
Click on the toolbar and select Gulp.js from the list. The Run/Debug Configuration: Gulp.js dialog opens.
Specify the name of the run configuration, the tasks to run (use blank spaces as separators), the location of the Gulpfile.js file where these tasks are defined, and the path to the gulp package installed under the current project root.
- Specify the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux.
Optionally, specify the environment variables for Node.js and the arguments for executing the tasks. Use the format
--<parameter_name> <parameter_value>, for example:
--env development. Learn more from the Gulp official website.
To run the tasks
Select the newly created run configuration from the list on the main toolbar and click next to the list. The output is displayed in the Run tool window.
To debug the tasks
Create a Gulp.js run/debug configuration as described above.
Open the Gulpfile.js file in the editor and set the breakpoints in it where necessary.
To run a Gulp task as a Before-Launch task
Open the Run/Debug Configurations Dialog dialog by choosing on the main menu, and select the required configuration from the list or create it anew by clicking and choosing the relevant run configuration type.
In the dialog that opens, click in the Before launch area and choose Run Gulp task from the list.
- In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
Running Gulp.js tasks automatically
On the Startup Tasks page that opens, click on the toolbar.
From the list, choose the required Gulp.js run configuration. The configuration is added to the list.
If no applicable configuration is available in the project, click and choose Edit Configurations. Then define a configuration with the required settings on the Run/Debug Configuration: Gulp.js page that opens. When you save the new configuration it is automatically added to the list of startup tasks.