Automate build tasks

[kungfux]

Type of change

• New feature (non-breaking change which adds functionality)

Description

Add tasks.json to automate typical tasks and improve dev experience.

Usage

• When you open a project, watch task automatically starts, so you don't have to run tasks/commands manually
• Press Ctrl+Shift+B to run build and watch task
• Run any task from VS Code UI or command palette

Additional info

Initial discussion has happened in 1781.
Documentation on tasks.

[cotes2020]

Thank you for adding this feature (though I believe the CLI is more efficient 😄 ). I have found some details that can be improved, which I will explain below.

[kungfux]

though I believe the CLI is more efficient 😄

I understand that. But isn't it nice to just open a project and not have to think about a repeatable step to start the server? Frankly, I forgot all the commands after a while, so having such a familiar way to execute commands is quite useful. 😊

[cotes2020]

I understand that. But isn't it nice to just open a project and not have to think about a repeatable step to start the server? Frankly, I forgot all the commands after a while, so having such a familiar way to execute commands is quite useful. 😊

Don't worry, OMZ plugins will help you remember the command line you have used.

For example, to run a startup script, just press a key . and ↑, and the command line will appear automatically:

cli.mov

[cotes2020]

To reduce the time we spend using GitHub's rudimentary review tools, I've directly presented an improved tasks configuration. What do you think?

tasks.json:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Run Jekyll Server",
      "type": "shell",
      "command": "./tools/run.sh",
      "group": {
        "kind": "build",
        "isDefault": true
      },
      "problemMatcher": [],
      "detail": "Runs the Jekyll server with live reload."
    },
    {
      "label": "Build Jekyll Site",
      "type": "shell",
      "command": "./tools/test.sh",
      "group": {
        "kind": "build"
      },
      "problemMatcher": [],
      "detail": "Build the Jekyll site for produnction."
    },
    {
      "label": "Build JS (watch)",
      "type": "shell",
      "command": "npm run watch:js",
      "group": {
        "kind": "build"
      },
      "problemMatcher": [],
      "detail": "Build JS files in watch mode."
    },
    {
      "label": "Build CSS",
      "type": "shell",
      "command": "npm run build:css",
      "group": {
        "kind": "build"
      },
      "problemMatcher": [],
      "detail": "Build CSS files."
    },
    {
      "label": "Build JS & CSS",
      "type": "shell",
      "command": "npm run build",
      "group": {
        "kind": "build"
      },
      "problemMatcher": [],
      "detail": "Build JS & CSS for production."
    }
  ]
}

[kungfux]

@cotes2020 I wanted to be able to have a task that would start build and watch for both Jekyll and JS. That's why I avoided using .sh scripts. However, in terms of simplicity and predictability, I have no objection to the proposed option. I still can use Ctrl+Shift+B and execute JS watch task when I need it 👍

[cotes2020]

Understood, you can add a group task to accomplish it, but it's recommended not to make it the default task because npm run ... are low-frequency tasks, plus, as discussed before, it has the problem of duplicate builds that consume startup time.

[kungfux]

I'm fine. Usually, I need just the Jekyll server, so it makes sense.

Do you want to apply your changes cause you completely redone the work ☺️ Just asking to not wait each other.

[cotes2020]

Yes, you can append a task similar to the one you wrote to meet your development requirements:

    {
      "label": "Start watch (Jekyll + NodeJS)",
      "dependsOn": [
        "Start watch (NodeJS)",
        "Start watch (Jekyll)"
      ],
      "group": {
        "kind": "build",
        // Jus dont set it as default, pls 
        // "isDefault": true
      }
    }

[cotes2020]

Good to go now