Skip to main content

Task runner for VS Code tasks.json

Project description

VS Code Task Runner

Ruff pre-commit GitHub license PyPi versions PyPi downloads


This is a command-line tool to execute VS Code tasks defined in the .vscode/tasks.json file. This allows you to write tasks once, and be able to run them in your editor, and in CI/CD. Basically, use .vscode/tasks.json as a Makefile.

This tool aims to be as feature-complete as possible with what VS Code supports for Windows, MacOSX and Linux. Much of the logic is taken directly from the VS Code source code and reimplemented in Python.

This pairs well with VS Code extensions that add buttons to run tasks such as actboy168.tasks.

Usage

Python 3.8+ is required.

Install with pip/pipx:

pip install vscode-task-runner

Use the command vtr on the command line and provide the label of the task(s). There must be a .vscode/tasks.json file in the working directory you run the command in. (You can also use the vscode-task-runner command instead if it makes you feel better).

Examples

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "pre-commit",
      "type": "shell",
      "command": "poetry run pre-commit run --all-files"
    }
  ]
}
$ vtr pre-commit
[1/1] Executing task "pre-commit": C:\Program Files\WindowsApps\Microsoft.PowerShell_7.3.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command poetry run pre-commit run --all-files
check json...............................................................Passed
check toml...............................................................Passed
check yaml...............................................................Passed
check for case conflicts.................................................Passed
trim trailing whitespace.................................................Passed
check for merge conflicts................................................Passed
mixed line ending........................................................Passed
poetry-check.............................................................Passed
poetry-lock..............................................................Passed
absolufy-imports.........................................................Passed
ruff.....................................................................Passed
black....................................................................Passed
pyleft...................................................................Passed
pyright..................................................................Passed
markdownlint.............................................................Passed

Additionally, for convenience, extra arguments can be tacked on to a task. For example, you can add extra settings or overrides when running in CI/CD. Continuing the example above:

$ vtr pre-commit --color=always --show-diff-on-failure
[1/1] Executing task "pre-commit": C:\Program Files\WindowsApps\Microsoft.PowerShell_7.3.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command poetry run pre-commit run --all-files --color=always --show-diff-on-failure
check json...............................................................Passed
check toml...............................................................Passed
check yaml...............................................................Passed
check for case conflicts.................................................Passed
trim trailing whitespace.................................................Passed
check for merge conflicts................................................Passed
mixed line ending........................................................Passed
poetry-check.............................................................Passed
poetry-lock..............................................................Passed
absolufy-imports.........................................................Passed
ruff.....................................................................Passed
black....................................................................Passed
pyleft...................................................................Passed
pyright..................................................................Passed
markdownlint.............................................................Passed

This can only be used when running a single task. You can also use -- as a separator to add additional arguments that do not start with a --. Example:

$ vtr test -- option1 option2
# This will run the task "test" with the arguments "option1" and "option2"

If your task uses an ${input:id} variable, you can provide the value for this variable as an environment variable named VTR_INPUT_{id}. Example:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "tests",
            "command": "pytest --cov=vtr/ --cov-report ${input:report_format}",
            "type": "shell"
        }
    ],
    "inputs": [
        {
            "id": "report_format",
            "description": "Coverage report format",
            "type": "pickString",
            "options": [
                "html",
                "xml",
                "annotate",
                "json",
                "lcov"
            ]
        }
    ]
}

Then in GitHub Actions:

  - name: Run tests
    run: vtr tests
    env:
      VTR_INPUT_report_format: html

The dependsOn key is also supported:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "install",
      "type": "shell",
      "command": "poetry install --sync"
    },
    {
      "label": "build",
      "type": "shell",
      "command": "poetry build",
      "dependsOn": ["install"]
    }
  ]
}
$ vtr build
[1/2] Executing task "install": C:\Program Files\WindowsApps\Microsoft.PowerShell_7.3.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command poetry install --sync
Installing dependencies from lock file

No dependencies to install or update

Installing the current project: vscode-task-runner (0.1.1)
[2/2] Executing task "build": C:\Program Files\WindowsApps\Microsoft.PowerShell_7.3.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command poetry build
Building vscode-task-runner (0.1.1)
  - Building sdist
  - Built vscode_task_runner-0.1.1.tar.gz
  - Building wheel
  - Built vscode_task_runner-0.1.1-py3-none-any.whl

You can also use it as a pre-commit hook if desired:

repos:
  - repo: https://github.com/NathanVaughn/vscode-task-runner
    rev: v0.1.7
    hooks:
      - id: vtr
        # Optionally override the hook name here
        # name: Build & Test
        args:
          - build # put the tasks you want to run here
          - test

The pre-commit hook does not match on any file types, and and will always execute.

If using pre-commit and poetry is part of your task, you may need to add the following

"options": {
    "env": {
        "VIRTUAL_ENV": "${workspaceFolder}${pathSeparator}.venv"
    }
}

and set virtualenvs.in-project to true.

Otherwise, poetry may think the pre-commit virtual environment is your project's virtual environment.

Implemented Features

  • Predefined variables:
    • ${userHome}
    • ${workspaceRoot}
    • ${workspaceFolder}
    • ${workspaceFolderBasename}
    • ${pathSeparator}
    • ${/}
    • ${defaultBuildTask}
    • ${cwd}
    • ${env:VARIABLE}
    • ${input:VARIABLE}
  • Settings hierarchy:
    • Global level settings
    • Global level OS-specific settings
    • Task level settings
    • Task level OS-specific settings
  • Task configuration:
    • cwd
    • env
    • type
      • "process"
      • "shell"
    • command
    • args
    • shell
      • executable
      • args
    • dependsOn
  • Quoting support:
    • "escape"
    • "strong"
    • "weak"

Unsupported Features

  • Any predefined variable not listed above. The other variables tend to rely upon the specific file opened in VS Code, or VS Code itself.
  • Variables scoped to workspace folders
  • Command variables
  • Input command variables
  • Problem matchers
  • Background tasks
  • UNC path conversion
  • Parallel dependsOn task execution
  • Task types other than "process" or "shell" (such as "npm", "docker", etc.)

Differences from VS Code

  • If a task is of type "shell", and a specific shell is not defined, the parent shell will be used
  • Only schema version 2.0.0 is supported
  • If no cwd is specified, the current working directory is used for the task instead
  • Does not support any extensions that add extra options/functionality
  • Does not load any VS Code settings
  • Extra arguments option
  • VTR_INPUT_${id} environment variables

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

vscode_task_runner-1.3.3.tar.gz (49.8 kB view details)

Uploaded Source

Built Distribution

vscode_task_runner-1.3.3-py3-none-any.whl (20.0 kB view details)

Uploaded Python 3

File details

Details for the file vscode_task_runner-1.3.3.tar.gz.

File metadata

  • Download URL: vscode_task_runner-1.3.3.tar.gz
  • Upload date:
  • Size: 49.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/5.1.1 CPython/3.12.7

File hashes

Hashes for vscode_task_runner-1.3.3.tar.gz
Algorithm Hash digest
SHA256 de57b3dfbebfe29bd178a88a43d0328b07e18f6da3afbdda881e94de832ec891
MD5 8b9faa344d1252f0362fa345af338633
BLAKE2b-256 0aaae78a2344b938ef46123f68b161634f777f1a229c305fca312c09e1b23439

See more details on using hashes here.

File details

Details for the file vscode_task_runner-1.3.3-py3-none-any.whl.

File metadata

File hashes

Hashes for vscode_task_runner-1.3.3-py3-none-any.whl
Algorithm Hash digest
SHA256 be0c7cfd0a3005e3aa1cfe23215e6cc32c50a3958bb77737669634cf1c4f6d1e
MD5 6adc808b7c1e5d6b9f03e965fd06247e
BLAKE2b-256 3d7e85b1d65291970124a2e5f85f8501e05eaedc2fa50659d804daae9fef0cfa

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page