How to run multiple tasks in VS Code on build?

Question

Using tasks.json version 2.0.0, I have not been able to make it so that, when I build my application, multiple tasks are run at the same time. I'm using gulp for my SCSS compilation, and running my Compile/minify cms.scss task on its own works fine, so it's not a problem with the task itself, just VS Code's task runner. When I Run Build Task in VS Code, my gulp task is not being run, even though it has "group": "build" — only the dotnet one is.

tasks.json

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "build",
            "command": "dotnet",
            "type": "process",
            "args": [
                "build",
                "${workspaceFolder}/HpsCoreWeb.csproj"
            ],
            "problemMatcher": "$msCompile",
            "group": {
                "kind": "build",
                "isDefault": true
            }
        },
        {
            "label": "Compile/minify cms.scss",
            "type": "gulp",
            "task": "cms.scss:cms.min.css",
            "problemMatcher": "$node-sass",
            "group": "build"
        }
    ]
}

According to the VS Code Tasks documentation:

group: Defines to which group the task belongs. In the example, it belongs to the test group. Tasks that belong to the test group can be executed by running Run Test Task from the Command Palette.

The dotnet build task is succeeding, so shouldn't the other task, which is also part of the build group, be run as well? What am I doing wrong?

Concertina

Answer 1

The problem is that "Run Test Task" and "Run Build Task" do not execute all tasks in that specific group. Usually you get a drop down selection so you can choose which task to execute. Since you have specified one of the tasks as default, the selection will be skipped and instead the default task is executed.

You can work around that by adding dependencies. Take the following example:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Echo 1",
            "command": "echo",
            "type": "shell",
            "args": [ "echo1" ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "dependsOn":["Echo 2"]
        },
        {
            "label": "Echo 2",
            "type": "shell",
            "command": "echo",
            "args": [ "echo2" ],
            "group": "build"
        }
    ]
}

As Echo 1 depends on Echo 2, Echo 2 will be executed prior to executing Echo 1. Note that the definition is a list, so more than one task can be specified. In that case the tasks are executed in parallel.

In your case adding "dependsOn":["Compile/minify cms.scss"] to your main build task should execute both tasks.

Cornaceous

My real project actually has many more gulp tasks. Does this mean that I have to essentially "daisy chain" them together (dotnet build depends on gulp1, which depends on gulp2, etc.) just to get them all to run? If it works, it works, but it's kind of astounding they don't simply have a way to asynchronously execute all tasks in a defined group without defining false dependencies. – Concertina

@JacobStamm Not an answer to your question, but if you're already using gulp it should be pretty straightforward to group your tasks there. In fact I'd expect that gulp's default would contain references to these tasks. – Gerrilee

@jacob-stamm No need to daisy chain them, you could add them all as dependencies to one task. I'm pretty sure they still don't run in parallel though. An other solution would be to write a batchfile/shellscript and invoke that. As of now (v1.27.2) I don't know of a better way to do it from within VS code. If it bothers you much, you could also file a feature request on github. The devs usually respond very fast. – Cornaceous

@G.G, so the dotnet build task's dependsOn would be ["gulp1", "gulp2"], etc. I believe that solves it :) Asynchronicity would be nice, but this does satisfy my question. I very well might submit a GitHub issue in VS Code's repo for this feature. – Concertina

I've confirmed that listing multiple tasks in dependsOn does execute them asynchronously – Concertina

Good to know! I've edited my answer to include that information as well – Cornaceous

There seems to be a dependsOrder option now with allowed values of parallel (Run all dependsOn tasks in parallel) or sequence (Run all dependsOn tasks in sequence). Default seems to be parallel. References: github.com/microsoft/vscode/blob/main/src/vs/workbench/contrib/… code.visualstudio.com/docs/editor/tasks#_compound-tasks – Illmannered

Answer 2

You can use Compound Tasks.

The example below executes "Client Build" and "Server Build" tasks when "Build" task is called.

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Client Build",
      "command": "gulp",
      "args": ["build"],
      "options": {
        "cwd": "${workspaceFolder}/client"
      }
    },
    {
      "label": "Server Build",
      "command": "gulp",
      "args": ["build"],
      "options": {
        "cwd": "${workspaceFolder}/server"
      }
    },
    {
      "label": "Build",
      "dependsOn": ["Client Build", "Server Build"]
    }
  ]
}

Pooka

This is great. Now I can do three things at once: start vite, serve laravel, and visit the localhost. I can write a (windows) script to do these but wanted a VSCode solution. – Humectant

Answer 3

Double check your settings are enabled for Gulp auto-detection:

"gulp.autoDetect": "on"

Sifuentes

It just so happens that my example uses gulp, whose auto-detection would remove the need to re-run gulp tasks on build. But my question is more about how to run multiple tasks on build in general, no matter what kinds of tasks they are. – Concertina

Answer 4

Add 'gulp-load-plugins' plugin in package.json

var gulpLoadPlugins = require('gulp-load-plugins'),
plugins = gulpLoadPlugins();

To read more about that plugin, see How To Build And Develop Websites With Gulp

Bosomed