Task Explorer - View and Run Tasks from Visual Studio Code

Description

Provides a view in either (or both) the SideBar and/or Explorer that displays all supported tasks organized into a treeview, with parent task file nodes, grouped nodes, and project folders (convenient for large multi-root workspaces). Tasks can be opened for view/edit, executed, and stopped. NPM file nodes support special npm command(s) (i.e. 'install') via context menu.

Table of Contents

• Task Explorer - View and Run Tasks from Visual Studio Code
  • Description
  • Table of Contents
  • Screenshots
  • Requirements
  • Features
  • Configuring Global Excludes and Apache Ant Includes with Glob Patterns
  • Internally Provided Tasks vs. VSCode Provided Tasks
  • Running bash/sh scripts in Windows Environment
  • Feedback & Contributing
  • Thank You
  • Settings

Screenshots

Original Explorer Tray	Sidebar View (v1.7)	Task Type Groups (v1.13)

Grunt/Gulp in Subfolders (v1.14)	Npm Commands (v1.16)

Requirements

• Visual Studio Code v1.30+

Features

• Check out the todo list (kept with Todo+)
• v1.19 - App-Publisher task support for BETA testing
• v1.18 - Added 'Add to excludes' action in task file node context menu
• v1.17 - Added 'Run last task' button to titlebar
• v1.16 - Added npm management tasks to npm file node context menus
• v1.15 - Support for gradle tasks (includes provider) (closes #15)
• v1.14 - Support for grunt and gulp task files not located in the project root (closes #12)
• v1.13 - Multiple task files of the same type placed within a group node for less clutter in folder level nodes
• v1.12 - Support for bash, batch, perl, powershell, python, ruby, and nsis scripts (includes provider)
• v1.11 - N/A - Obsolete Batch Task Provider replaced by v1.12 ScriptProvider
• v1.10 - Support for Makefiles (includes provider)
• v1.9 - Support for gulp and grunt tasks (includes provider)
• v1.8 - Support for ant files not named [Bb]uild.xml, ansicon output colorization fixed
• v1.7 - Two view types - Use one or both of either SideBar View and/or Explorer Tray
• v1.6 - Progress icons for running tasks
• v1.6 - Stop execution button for running tasks
• v1.5 - Support for Apache Ant tasks (includes provider)
• v1.4 - Support for TSC tasks
• v1.3 - Support for Visual Studio Code tasks
• v1.2 - Convenient layout - groups all tasks by project folder, by task file, by task
• v1.1 - Supports multi-root or single-root workspaces
• v1.0 - Open and launch NPM scripts as tasks

Configuring Global Excludes and Apache Ant Includes with Glob Patterns

The setting 'exclude' defines a string or an array of strings of file patterns to ignore. The setting applies to all script types. The string(s) must be glob pattern(s), for example:

• taskExplorer.exclude: [ "**/.vscode-test/**", "**/vendor/**", "**/out/**", "**/output/**" ]

Note that the glob pattern "**/node_modules/**" is applied by default to the excludes list in all cases.

Since Apache Ant uses a .xml file extension, the setting 'includeAnt' can be used to specify other file names other than [Bb]uild.xml to include as ant files so that all xml files do not need to be searched (slowing down tree refreshes in large workspaces or project with a large number of various xml files). The setting is a string or an array of strings and must be glob pattern(s) including the .xml extension, for example:

• taskExplorer.includeAnt: [ "**/extraTasks.xml", "**/scripts/ant/*.xml" ]

Note that the glob pattern "**/[Bb]uild.xml" is applied by default to the ant includes list in all cases.

Internally Provided Tasks vs. VSCode Provided Tasks

The following tasks are provided by VSCode:

• Workspace (.vscode/tasks.json)
• NPM (**/package.json)

All other tasks are internaly provided. Workspace tasks are detected by VSCode in all cases. However, NPM tasks are detected only if the setting 'Npm -> Auto Detect' is turned on in VSCode Settings. By default this is turned on, but if NPM tasks are not displaying, please check this setting, also check the setting that turns npm package management off in favor of Yarn 'Npm -> Package manager'. A future release will contain internally provided NPM and Yarn tasks.

Detection of all internally provided task types can be turned on/off in Settings - 'Task Explorer -> Enable [Tasktype]'.

Running bash/sh scripts in Windows Environment

Bash/sh scripts in Windows will have the shell executable automatically set to a bash shell (if the default shell set in VSCode is not bash). The shell executable used can be set in Settings using the pathToBash setting. If there is no value set in Settings, and Git Bash exists at the default installation installation, Git Bash will be used (MinGW). If Git Bash does not exist at the default install location, it is assumed the the path to bash.exe is part of the system PATH variable. If you experience errors running Bash scripts in Windows, please check these items.

Feedback & Contributing

• Please report any bugs, suggestions or documentation requests via the Issues
• Feel free to submit pull requests
• Contributors

Thank You

• The Material Icon Theme for some of the task type icons.
• The author of the NSIS Extension idleberg for NSIS graphics.

Settings