Task Master will automatically trawl your project directory for task scripts, e.g. npm, gulp, shell, python, ruby, powershell, perl scripts etc... and allow you to execute each task with the click of a mouse!
The days of having to configure a task runner per project, or manually type out task scripts are over!
Never configure a task runner or manually type out task scripts again!
Automatically search for tasks inside the current active project.
Execution of tasks through Status Bar Menu.
Task Master will automatically search for and configure tasks for new project.
Supports NPM Tasks.
Supports Gulp Tasks.
Supports Shell Scripts.
Supports Python Scripts.
Supports Ruby Scripts.
Supports Perl Scripts
Supports Powershell Scripts (Experimental)
Other than NPM or Gulp? None.
But if you're lazy (like me) and you don't like typing out task scripts or configuring the task runner everytime you switch projects then this extension is definitely for you.
Fixed a bug where task command would be populated as text in editor window.
Greatly improved parsing of gulpfiles and tasks in general.
Tasks will now launch in their own terminal window.
Fixed support for vscode 1.6.*.
Added new user preference option to manually determine gulp tasks location.
Added new user preference option to manually determine npm tasks location.
Added user preference settings to enable or disable scanning filetypes.
Added user preference setting to control the excludes glob.
Improved performance of task scanning.
Fixed a bug where .sh scripts would sometimes not register.
Task dropdown selector now sorted alphabetically.
Added support for Perl scripts.
Added support for Powershell scripts (Experimental).
Improved deep linking of nested tasks.
Added support for Ruby scripts.
Added support for Python scripts.
Reduced scanning time of tasks.
Improved parsing of files to no longer include false positive gulp tasks.
node_modules is now omitted from shell script scan.
There is currently a known issue in VSCode 1.4 on Windows with runSelectedTasks method. This is known to Microsoft and hopefully should be resolved (or switched out) in v1.5.
I'm aware of this issue and have coded around it.