Task Explorer - View and Run Tasks from Visual Studio Code
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, among other things for specific task types, for example NPM file nodes support common npm command(s) (i.e. 'install') via context menu.
Table of Contents
Screenshots by Version
Features by Version
Configuring Global Excludes and Apache Ant Includes
The setting exclude defines a file/directory pattern or an array of file/directory patterns to ignore using Glob Patterns or a valid File URI. The setting applies to all script types. For example:
Note that the glob pattern "**/node_modules/**" is applied by default to the excludes list in all cases. Using the exclude configuration can greatly improve performance in large workspaces if configured correctly.
Task files that are found by Task Expolorer can also be added to the excludes list via the tree node context menu, by right clicking the task file or task group node, and selecting Add to Excludes.
Apache Ant uses an .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 defines a file pattern or an array of file patterns to include using Glob Patterns or a valid File URI, for example:
Note that the glob pattern "**/[Bb]uild.xml" is applied by default to the Ant includes list in all cases. If you don't include the asterisked glob pattern
Ant and Gulp Self Provided Tasks
By default, a custom parser is used to locate Ant and Gulp tasks in respective files. This may be fine in most cases, but in cases where the script and/or build files become complex, or there is something in the file that was not coded into the parser, you can use the ant and gulp programs themseleves to find their own tasks. Note however that turning this on has a negative performance impact when refreshing and providing tasks to the VSCode Task Host.
Using Groups With A Separator
EXPERIMENTAL The Groups With Separator option is simply an extra level of task groupings that can be made based on a configured separation character in the script name. This option can be turned on/off with the Group With Sepator option in Settings, the default is OFF. The default separator is a dash ("-").
For example, consider 10 npm tasks, 5 of which all start with the string dev-, 5 of which start with the string prod-. Prior to Version 1.23, this would create 10 individual task nodes within the main npm task node in the task tree:
By enabling the Group With Sepator option in Settings and setting the Group Sepator to a dash ("-") two new grouped nodes would be created underneath the main npm node, one called dev and the other called prod. Each of these two sub-nodes of course would contain the respective dev- and prod- scrtips/tasks, minus the prepended group name:
Internally Provided Tasks vs. VSCode Provided Tasks
The following tasks are provided by VSCode:
All other tasks are internaly provided. Workspace tasks are detected by VSCode in all cases. However, NPM tasks are detected only if the setting
Detection of all internally provided task types can be turned on/off in Settings -
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
Feedback & Contributing
Rate It - Leave Some Stars
Please rate your experience with stars... like five of them ;)
Other Code Extensions by spmeesseman
If my work and this extension has made your life easier, consider a donation. All donations go straight to the Single Dad ATM.
3/25/20 - CI has to be THE most overrated tech on the planet. CI should be named PA standing for "pain in the ass". These are personal notes for correcting CI issues that happen seemingly every other release.
When semantic release kindly creates the git version tag, then something bombs, run the following git commands to remove the git tag, remote and local:
Errors in reelase when incuding babel runtime:
WHen messing with babel, and finishing, install/uninstall the runtime: