Task Explorer - View and Run Tasks from Visual Studio Code

Description

Provides an organized view in either (or both) the SideBar and/or Explorer that conveniently displays all supported tasks, organized into a treeview, with parent task file nodes and project folders (perfect for large multi-root workspaces). Tasks can be opened for view/edit, executed, and stopped. 'npm install' is supported in the context menu of all npm file nodes.

Screenshots

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

Grunt/Gulp in Subfolders (v1.14)

Requirements

• Visual Studio Code v1.30 or higher
• To display npm, grunt, and gulp tasks, the 'Auto Detect' setting must be turned 'On' in VSCode for each respective task provider.
• Some task types inherit the associated file type icon from VSCode when displayed in the task tree. You must have an icon set installed and active (for example, the Material Icon Theme) for these task types to display icons in the tree nodes.

Features

• Check out the todo list
• v1.14 - Support for grunt and gulp task files not located in the project root
• v1.13 - Multiple task files of the same type are now placed within a group node for less clutter in folder level nodes
• v1.12 - Script Task Provider - Open and launch bash, batch, perl, powershell, python, ruby, and nsis scripts
• v1.11 - N/A - Obsolete Batch Task Provider replaced by v1.12 ScriptProvider
• v1.10 - Makefile Task Provider - Open and launch C/C++ Makefile targets
• v1.9 - Support for gulp and grunt tasks
• 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 - Ant task provider - Open and launch ANT targets as tasks
• v1.4 - Open and launch TSC tasks
• v1.3 - Open and launch 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 excludes and 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.

The setting 'includeAnt' is a string or an array of strings used to define file patterns to include which would have normally been ignored by the internal Ant Task Provider. By default, only ant files named [Bb]uild.xml are considered. The string(s) must be glob pattern(s) and should include the .xml extension, for example:

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

Grunt and Gulp Task Providers

VSCode includes task providers for Grunt and Gulp internally. The Grunt and Gulp task providers in this extension (introduced in v1.14) will ignore grunt and gulpfiles in the root project directory in lieu of that fact, i.e. it will only provide tasks located in subdirectories of the project root. Note that the internal VSCode Gulp provider will not even refresh your tasks if you edit your gulp file. In a future release, settings will be added to include files found in the project root, where a user can turn off internal VSCode task detection for gulp and/or grunt.

Feedback & Contributing

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

Settings