Coder Social home page Coder Social logo

spmeesseman / vscode-taskexplorer Goto Github PK

View Code? Open in Web Editor NEW
137.0 2.0 27.0 48.03 MB

Run and Manage Tasks for Visual Studio Code

License: Other

TypeScript 53.53% JavaScript 2.49% Batchfile 2.77% PowerShell 0.01% Shell 8.73% Python 1.17% Makefile 0.09% Perl 1.22% XSLT 30.01%

vscode-taskexplorer's Introduction

Task Explorer - View and Run Tasks from Visual Studio Code

PROJECT ON HOLD

IF YOU HAVE KIDS, HUG THEM. EVERY CHANCE YOU GET

I LOST MY DAUGHTER ALMOST A YEAR AGO, EACH AND EVERY DAY IS FILLED WITH OVERWHELMING SADNESS AND TEARS

I AM... FOREVER BROKEN.

The most downloaded task related extension on the Marketplace

authors Installs Downloads Ratings PayPalDonate

codecov CodeFactor app-publisher

GitHub issues open GitHub issues closed GitHub pull requests GitHub last commit

src0 src1 src0y src2 src3 src13 src4 src5 src6 src7 src8 src9 src10 src11 src12 src13

IMPORTANT NOTE: This extension has surpassed where I was ever going to take it, and the time that ended up going into it were more than I ever intended. Considering a pay scheme (cheap, e.g. $10 - $20), with free usage up to the # of to-be-determined number of parsed tasks. Note the license, this codebase is NOT permitted to be copied or distributed without my permission.

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, 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

Original Explorer Tray Sidebar View (v1.7) Task Type Groups (v1.13)
ss0 ss1 ss2
Grunt/Gulp in Subfolders (v1.14) Npm Commands (v1.16) Task Groupings (v1.23)
ss4 ss5 ss6
Multi-Level Task Groupings (v1.29) Run with Args, No Terminal (1.30) Last Tasks (1.25) Favorites (2.0)
ss7 ss8 ss9

Requirements

  • Visual Studio Code v1.50+

"Should" work with VSCode versions 1.30 and above, but am no longer running tests against VSCode versions below 1.50 as of 2/5/2021 (v1.28.0).

Features by Version

  • v2.7 - External provider integration API #22
  • v2.6 - Composer support #150 Include shellscripts with no extension #153 Rename tasks #164
  • v2.5 - Webpack build - Runs 10-15% faster.
  • v2.4 - Add Pipenv support for Python Pipfile scripts. (thanks rob4226) #155
  • v2.3 - App-Publisher v2.0 support. Several fixes including long time issue #143.
  • v2.2 - Support for Maven (closes #107)
  • v2.1 - App Publisher changelog pull tasks
  • v2.0 - All async-await processing, Favorites (closes #101), Clear special task lists
  • v1.30 - Configurable default click action (closes #97), Add 'Run with Arguments' command (closes #88), Add 'Run with NoTerminal' command (closes #39) (note that as of VSCode 1.53, there seems to be a bug that prevents running tasks without showing the terminal).
  • v1.29 - Support multi-level task groupings (closes #129), Support user tasks (closes #127)
  • v1.28 - Support Makefile aliases (thanks MichaelCurrin)
  • v1.27 - Use gulp and ant to find their respective tasks (configurable on/off) (closes #105), Make grouping separator configurable (thanks richarddavenport)
  • v1.26 - Add 'Running Task' status bar message (refs #47)
  • v1.25 - Add 'Last Tasks' pseudo-folder
  • v1.24 - Add 'Open Terminal' button to running tasks (closes #23)
  • v1.23 - Task groupings with dashed task groups (Off by default)
  • v1.22 - Major performance enhancements - Task Tree / Task Scanning
  • v1.21 - Add option to keep terminal open after stopping task (closes #51)
  • v1.20 - Add support for restarting task (thanks antfu)
  • v1.19 - App-Publisher task support for BETA testing
  • v1.18 - Add 'Add to excludes' action in task file node context menu
  • v1.17 - Add 'Run last task' button to titlebar
  • v1.16 - Add 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

Version 2

Version 2 highlights 2 major performance enhancements along with several features and bug fixes, notably:

  1. An async/await approach for all processing has improved task load time performance 10-20%.
  2. Launching tasks is more than 2x more responsive in the Tree UI, as well as when tasks finish.
  3. Favorites List.
  4. Clear buttons for Favorites and last Tasks lists (need icon!!!).
  5. Much improved logging for debugging user issues.
  6. Completely refactored classes, interfaces, and commenting for easier community contributions.

App-Publisher

app-publisher-cmdline-banner

Integrates with the app-publisher tool.

App-Publisher is a multi-purpose versioning/release tool that can be used for, but not limited to, the following:

  • Publish releases in a CI like manner on a local system, with version calculation.
  • Several task-mode tasks such as generating the next version from commit message subjects.
  • NPM releases.
  • GitHub Releases.
  • MantisBT releases via the Releases Plugin.
  • View/output changelogs for a pending release.

ap0

Configuring Global Excludes, Apache Ant and Bash Globs

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:

  • taskExplorer.exclude: [ "**/.vscode-test/**", "**/vendor/**", "**/out/**", "**/output/**", "/c:/projects/project1/src/theme/test/package.json" ]

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 Explorer 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 globPatternsAnt 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:

  • taskExplorer.globPatternsAnt: [ "**/extraTasks.xml", "**/scripts/ant/*.xml", "/c:/projects/project1/scripts/test/antetests.xml" ]

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 **/ first in the string, files in sub-folders will not be found.

In the same way as for Ant tasks, Bash scripts without extensions can be configured to be found by the Bash Task Provider by using glob patterns in the same way, with the globPatternsBash setting:

  • taskExplorer.globPatternsBash: [ "**/bash_scripts/**", "**/sh/scripts/**", "/usr/local/bin/start_task" ]

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 themselves 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 Seperator 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:

npm
    dev-build
    dev-build-server
    dev-build-themes
    dev-cp-from-bin
    dev-clean
    prod-build
    prod-build-server
    prod-build-themes
    prod-cp-from-bin
    prod-clean

By enabling the Group With Separator option in Settings and setting the Group Separator 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- scripts/tasks, minus the prepended group name:

npm
    dev
        build
        build-server
        build-themes
        cp-from-bin
        clean
    prod
        build
        build-server
        build-themes
        cp-from-bin
        clean

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 internally 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. Note these tasks are still displayed in the Task Tree, just not "provided" by this extension.

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.

Running Task Icon Animations

FOr whatever reason, on some systems the animated running task icon eats a lot of CPU. If this is your case, the animated icon can be turned off in settings (on by default).

Parsing Reports

For debugging or curiosity, a report can be generated listing all parsed components and the properties found. You can generate a report in the explorer context menus using the Task Explorer: View Parsing Report menu item.

parsing-report-img

External Provider Integration API

Any extension that implements TaskProvider (specifically it's provideTasks method) can add it's tasks to the Task Explorer tree. To register an external provider with Task Explorer, follow these steps:

Get the TaskExplorer API object:

const teApi = await vscode.commands.executeCommand("taskExplorer.getApi");

Alternatively, using the Task Explorer type definitions:

let teApi;
const taskExplorer = extensions.getExtension("spmeesseman.vscode-taskexplorer");
if (taskExplorer && taskExplorer.isActive)
{
    teApi = taskExplorer.exports as TaskExplorerApi;
}

Note: Before using any of the API functions, check busy status using the teApi.isBusy API function first, to ensure the indexer is not running.

Register the instance of TaskProvider or ExternalExplorerProvider using the register method of the Task Explorer API object:

await teApi.register("taskTypeName", myProvider as TaskProvider);

Where taskTypeName is the name of the task type, i.e. "npm", "ant", "gulp", etc, and myProvider is the instance of TaskProvider that implements the provideTasks method.

Any provider(s) should be unregistered in the deactivate method of an extension, to remove a provider:

await teApi.unregister("taskTypeName");

Where taskTypeName is the name of the task type, i.e. "npm", "ant", "gulp".

You can optionally install the Task Explorer API types:

npm install @spmeesseman/vscode-taskexplorer-types

The provided tasks must implement the taskExplorer.external task interface:

{
    script: "the task name",
    target: "command to run",
    path: "file path",
    fileName: "file name",
    uri: file `Uri`,
    taskItemId: (internal use, ignore),
    icon: {
        light: "/path/to/light.svg",
        dark: "/path/to/dark.svg"
    }
}

The task definition must also define most of the interface properties in the package.json, for completeness, the entire definition is:

"taskDefinitions": [
{
    "type": "extjs",
    "required": [],
    "properties": {
        "script": {
            "type": "string",
            "description": "taskdef.task.script"
        },
        "target": {
            "type": "string",
            "description": "taskdef.task.target"
        },
        "cmdLine": {
            "type": "string",
            "description": "taskdef.task.cmdLine"
        },
        "fileName": {
            "type": "string",
            "description": "taskdef.task.fileName"
        },
        "icon": {
            "type": "string",
            "description": "taskdef.task.icon"
        },
        "iconDark": {
            "type": "string",
            "description": "taskdef.task.icon.dark"
        },
        "isDefault": {
            "type": "boolean",
            "description": "taskdef.task.isDefault"
        },
        "path": {
            "type": "string",
            "description": "taskdef.task.path"
        },
        "taskItemId": {
            "type": "string",
            "description": "taskdef.task.taskItemId"
        },
        "uri": {
            "type": "object",
            "description": "taskdef.task.fileUri"
        }
    }
}]

The definition will be reduced in the future. This definition is remnant of Task Explorer's early days and is in need of a cleanup.

For reference, the entire Task Explorer API object is:

interface TaskExplorerApi
{
    log: any;
    utilities: any;
    fileCache: any;
    explorerProvider: TaskTreeDataProvider | undefined;
    sidebarProvider: TaskTreeDataProvider | undefined;
    taskProviders: Map<string, TaskExplorerProvider>;
    registerProvider(providerName: string, provider: TaskProvider): void;
    unregisterProvider(providerName: string): void;
}

Putting it all together:

async function activate()
{
    ... other code ...
    const taskProvider = new ExtJsTaskProvider();
    context.subscriptions.push(tasks.registerTaskProvider("extjs", taskProvider));
    registerWithTaskExplorer(taskProvider);
    ... other code ...
}

async function deactivate()
{
    ... other code ...
    const taskExplorer = extensions.getExtension("spmeesseman.vscode-taskexplorer");
    if (taskExplorer && taskExplorer.isActive && taskExplorerRegistered)
    {
        const teApi = taskExplorer.exports as TaskExplorerApi;
        await teApi.unregister("extjs");
    }
    ... other code ...
    return Promise.resolve();
}

function registerWithTaskExplorer(taskProvider: ExternalExplorerProvider)
{
    const taskExplorer = extensions.getExtension("spmeesseman.vscode-taskexplorer");
    if (taskExplorer && taskExplorer.isActive)
    {
        const teApi = taskExplorer.exports as TaskExplorerApi;
        if (!teApi.isBusy())
        {
            await teApi.register("taskTypeName", taskProvider);
            taskExplorerRegistered = true;
        }
        else {
            setTimeout(() => registerWithTaskExplorer(taskProvider), 1000);
        }
    }
    else
    {
        setTimeout(() => registerWithTaskExplorer(taskProvider), 5000);
    }
}
  • As of v2.7.0, the external task API has not been formally tested, a. Who will be the guineau? Hahaha ;)
  • As of v2.7.0, the API does not support custom icons from the task definition, but for extension testing you can place an icon in res/sources or res/dark / res/light of the TaskExplorer installation folder, named using the same task type name in the registerProvider call mentioned above, and will be used by the Task Explorer tree.

Feedback & Contributing

Rate It - Leave Some Stars

Please rate your experience with stars... like five of them ;)

Thank You

Icon Contributors:

Other Contributors:

  • antfu
  • eamodio (fixed #114)
  • MichaelCurrin
  • tiansin
  • JacobParis
  • Spitfire1900

Open Source Projects

Package Use Case Repository Marketplace
app-publisher Release Automation / CI GitHub Npmjs.org Registry
arg-parser Node Argument Parser GitHub Npmjs.org Registry
code-package Code Dev Environment GitHub GitHub Releases
env-ci CI ENvironment Detection GitHub Npmjs.org Registry
extjs-pkg-filterbar ExtJS Grid Filter Bar GitHub Npmjs.org Registry
extjs-pkg-fontawesome ExtJS FontAwesome Integration GitHub Npmjs.org Registry
extjs-pkg-fontawesome-pro ExtJS FontAwesome Pro Integration GitHub Npmjs.org Private Registry
extjs-pkg-intltelinput ExtJS IntlTelInput Wrapper GitHub Npmjs.org Registry
extjs-pkg-mantis ExtJS MantisBT Integration GitHub Npmjs.org Registry
extjs-pkg-plyr ExtJS Plyr Wrapper GitHub Npmjs.org Registry
extjs-pkg-tinymce ExtJS TinyMCE Wrapper GitHub Npmjs.org Registry
extjs-pkg-websocket ExtJS WebSocket Wrapper GitHub Npmjs.org Registry
extjs-pkg-webworker ExtJS WebWorker Wrapper GitHub Npmjs.org Registry
jenkins-mantisbt-plugin Jenkins MantisBT Integration GitHub Npmjs.org Registry
jenkins-utility-server Jenkins Desktop Server GitHub Npmjs.org Registry
mantisbt MantisBT Custom Site GitHub GitHub Releases
ApiExtend MantisBT API Extensions GitHub GitHub Releases
CommitReact MantisBT Post Commit Actions GitHub GitHub Releases
GanttChart MantisBT Gantt Chart GitHub GitHub Releases
IFramed MantisBT IFramed Pages GitHub GitHub Releases
ProjectPages MantisBT Custom Nav Buttons GitHub GitHub Releases
Releases MantisBT Releases Management GitHub GitHub Releases
SecurityExtend MantisBT SPAM Filter GitHub GitHub Releases
ServerFiles MantisBT Server File Editor GitHub GitHub Releases
svn-scm-ext VSCode SVN Extension GitHub Visual Studio Marketplace
vscode-extjs VSCode ExtJS Intellisense GitHub Visual Studio Marketplace
vscode-taskexplorer VSCode Tasks Management GitHub Visual Studio Marketplace
vscode-vslauncher VSCode VS Project Launcher GitHub Visual Studio Marketplace

Donations

If my work and this extension has made your life easier, consider a donation. All donations go straight to the Single Dad ATM.

vscode-taskexplorer's People

Contributors

antfu avatar eamodio avatar greenkeeper[bot] avatar idleberg avatar jacobparis avatar michaelcurrin avatar richarddavenport avatar rob4226 avatar semantic-release-bot avatar spitfire1900 avatar spmeesseman avatar tiansin avatar wdhongtw avatar yzptsubasa avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

vscode-taskexplorer's Issues

settings as tables

edit that

"taskExplorer.enableAnt": true,
"taskExplorer.enableBash": true,
"taskExplorer.enableGradle": true

to

"taskExplorer.enable": {
    "ant": true,
    "bash": true,
    "gradle": true
}

edit that

"taskExplorer.pathToAnt": "ant.exe",
"taskExplorer.pathToPython": "python.exe",
"taskExplorer.pathToGradle": "gradlew.bat"

to

"taskExplorer.paths": {
    "ant": "ant.exe",
    "python": "python.exe",
    "gradle": "gradlew.bat"
}

An in-range update of vsce is breaking the build 🚨

The devDependency vsce was updated from 1.60.0 to 1.61.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

vsce is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 5 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Gulp tasks cannot be executed and retrieved

1

@spmeesseman Cannot identify such a task code with a newline.

I ran the gullp task in the subdirectory and got an error that I couldn't find the gulp binary.
> Executing task: /Users/johnny/admin2/node_modules/.bin/gulp default <

My Gulpfile.js is in /Users/johnny/admin2/public/admin directory.

The Gulpf binary is in this directory.
/Users/johnny/admin2/public/admin/node_modules/.bin/gulp

An in-range update of eslint-plugin-prettier is breaking the build 🚨

The devDependency eslint-plugin-prettier was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

suggestion: clicking on the task could switch to the task terminal if active

I think it would be cool if clicking on a running task would focus the terminal that's running such task (be it by clicking it directly when it is running, via some setting or through a button near the "stop" button)

Or maybe double clicking + button
Also double clicking could start a task if not already started

Use NSIS v3 logo

I've just stumbled across this extension and noticed it is still using the old NSIS logo. You can find the NSIS v3 logo on GitHub and even npm. Let me know if you need help, e.g. if you prefer the bitmap icons used by NSIS itself.

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 12.12.12 to 12.12.13.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Please add "taskExplorer.pathToPowershell" setting

Hello,

it is possible to have 2 different powershell versions installed on windows systems (powershell 5 and 6). Because of this, it would be great to have the possibility to set the path to the preferred powershell version to be used by vscode-taskexplorer.

By default powershell 5 is used but what if someone want to use powershell 6?

Can you please add a possibility to set the executable path in vscode settings.json?

Thanks!

An in-range update of conventional-changelog-spm is breaking the build 🚨

The devDependency conventional-changelog-spm was updated from 1.0.1 to 1.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

conventional-changelog-spm is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v1.1.0

1.1.0 (2019-04-06)

Build System

  • semantic-release: no patch on docs edit [skip ci] (128bfb0)
  • semantic-release: use module itself as changelog generator (f4c28dc)

Documentation

  • readme: add Greenkeeper badge (e8894b5)
  • readme: update badges layout [skip ci] (0627abc)
  • license: update info (b06ae2e)
  • readme: update initial info [skip ci] (373324e)

Features

  • add subjectKeywords config for adding specific sections to changelog (abd2dd8)

Styles

  • add eslint config file (dd3950b)
  • js: add jsbeautify config file (13a8c68)
Commits

The new version differs by 12 commits.

  • 7e5f535 chore(release): 1.1.0 [skip ci]
  • abd2dd8 feat: add subjectKeywords config for adding specific sections to changelog
  • f4c28dc build(semantic-release): use module itself as changelog generator
  • dd3950b style: add eslint config file
  • 13a8c68 style(js): add jsbeautify config file
  • b06ae2e docs(license): update info
  • 0627abc docs(readme): update badges layout [skip ci]
  • 265ff87 Merge pull request #1 from spmeesseman/greenkeeper/initial
  • e8894b5 docs(readme): add Greenkeeper badge
  • dfc329c ci(azure): initial config file
  • 373324e docs(readme): update initial info [skip ci]
  • 128bfb0 build(semantic-release): no patch on docs edit [skip ci]

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.13.26 to 15.13.27.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v15.13.27

15.13.27 (2019-10-18)

Bug Fixes

  • ignore custom port when converting ssh repo URL to https (4af8548)
Commits

The new version differs by 3 commits.

  • 3438ec5 test: fix typo in test examples
  • 4af8548 fix: ignore custom port when converting ssh repo URL to https
  • dc19dfa docs: remove unnecessarily apostrophe

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of cz-conventional-changelog is breaking the build 🚨

The devDependency cz-conventional-changelog was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cz-conventional-changelog is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v3.0.3

3.0.3 (2020-01-28)

Bug Fixes

  • Update conventional-commit-types to the latest version 🚀 (#105) (5a371c1)
Commits

The new version differs by 1 commits.

  • 5a371c1 fix: Update conventional-commit-types to the latest version 🚀 (#105)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Add ability to run default ANT task

First, thanks for such a useful extension. This is exactly what I've been wanting!

I would love to see the "default" ANT task supported, by offering a "play" button to the right of the build name (like you see when viewing the individual tasks in the ANT build script).

We have a large code base that uses lots of ANT scripts. They all have a default task defined, but unfortunately the default task name is standardized, so I don't always remember which task I need to run.

If there was a play button to right of each ANT task that has a "default" task configured, this would make things much easier. Just click the play button to run the task.

Ant file import lookup

If in a build.xml file other xml file for ant are imported via a fileset it would be nice if that would be resolved.

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 11.12.0 to 11.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

gulp tasks are not detected

As the title says, gulp tasks are not detected.

My gulpfile.js is written according to the official documentation and the tasks are accordingly exported in this way:

const { series } = require('gulp');

// The `clean` function is not exported so it can be considered a private task.
// It can still be used within the `series()` composition.
function clean(cb) {
  // body omitted
  cb();
}

// The `build` function is exported so it is public and can be run with the `gulp` command.
// It can also be used within the `series()` composition.
function build(cb) {
  // body omitted
  cb();
}

exports.build = build;
exports.default = series(clean, build);

Running gulp from terminal correctly detects, shows and executes them:

> gulp --tasks
[14:52:29] Tasks for ~/test/gulpfile.js
[14:52:29] ├── build
[14:52:29] └─┬ default
[14:52:29]   └─┬ <series>
[14:52:29]     ├── clean
[14:52:29]     └── build

I tried with some other extensions (i.e. this one) and they can detect and run them.

Could it be possible to fix this? If there is some more info that I can provide, please ask.

An in-range update of mocha-junit-reporter is breaking the build 🚨

The devDependency mocha-junit-reporter was updated from 1.23.1 to 1.23.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha-junit-reporter is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 9 commits.

  • 9787677 1.23.2
  • c612b17 Bump js-yaml from 3.13.0 to 3.13.1
  • b30afd0 add default values in option table
  • bcfc7a4 Ensure that test time attribute is capped at 4 digits after the decimal
  • 19eee3e Update options parsing for mocha 6+
  • 3b310cc Bump lodash from 4.17.11 to 4.17.15
  • 1993678 Un-IDE the path
  • ed7a698 Do workflows work?
  • 9168d01 Fixed unhandled promise rejection

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Add configuration option to not show the Terminal when a task is run

I would love to have a flag which would cause the auto-detected tasks to not open up the Terminal view when a task is run (ie. a "silent" execution). The task's output would still be accessible on-demand in the Terminal view but the view itself would remain hidden unless explicitly shown by the user.

I execute compile tasks almost after every file save and get quite annoyed by the terminal view constantly popping out. Most of the time I am only interested in seeing the final result (success/failure) of a task run which I can see in the status bar anyway.

Thank you for consideration! ❤️

An in-range update of @types/semver is breaking the build 🚨

The devDependency @types/semver was updated from 6.0.2 to 6.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/semver is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Support for compound tasks?

Hi, are you planning on supporting compound tasks? They are specified using dependsOn

Compound tasks should have their children as leaves in the tree view and their actions – ie start/stop – could forEach those actions into their children tasks.

An in-range update of vsce is breaking the build 🚨

The devDependency vsce was updated from 1.71.0 to 1.72.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

vsce is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 12 commits.

  • 2ca36aa 1.72.0
  • e4a8df5 fixes #415
  • 7eba451 Revert "Merge pull request #411 from felixhao28/master"
  • 6e5c2d5 Merge pull request #412 from xontab/bugfix/changed-log-level-error-exec-npm
  • ef3322b Merge branch 'master' into bugfix/changed-log-level-error-exec-npm
  • 2a02458 Merge pull request #411 from felixhao28/master
  • 2844e5b Merge pull request #409 from wraith13/patch-1
  • 845eb79 Update README.md
  • e0d73c9 Minor refactoring
  • 2e003b0 Changed loglevel to error when listing deps using npm list command
  • 4302d01 Support linked npm modules
  • 2d8dc60 Modifying messages to match the current situation

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Show all available Gradle tasks in explorer

Only user defined tasks are shown. Gradle also have plugins, which add more tasks. In the example file only the 'fatJar' task is shown, but there are a number of tasks, like build, jar, check, eclipse, javadoc etc.

You can check all those tasks running 'gradle -b test.gradle tasks --all' (there's no need to specify the file with the '-b' switch if this file was named build.gradle). Task is a task that show the available tasks. The build, check, jar and javadoc tasks are included with the java plugin and the eclipse task is included with the eclipse plugin.

Originally posted by @francilioaraujo in #15 (comment)

Add option to use yarn or pnpm instead of plain npm

When right clicking on the grouped npm tasks, there is a list that contain some voices like Run npm install or Run npm update.

It would be useful to be able to select which package manager one wants to use instead of the default npm, maybe an option can be added where one can select if these commands should be run instead with yarn or pnpm.

Alternate Gulpfile Names are Not Supported

Gulp supports writing the Gulpfile in languages other than Javascript, taking advantage of a transpiler, like Babel. The documentation isn't thorough, but from experience, I know at least the following filenames are supported:

  • gulpfile.js
  • gulpfile.babel.js
  • gulpfile.ts
  • gulpfile.babel.ts

An in-range update of @semantic-release/changelog is breaking the build 🚨

The devDependency @semantic-release/changelog was updated from 3.0.3 to 3.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/changelog is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v3.0.4

3.0.4 (2019-05-14)

Bug Fixes

  • package: update fs-extra to version 8.0.0 (50ed752)
Commits

The new version differs by 3 commits.

  • 50ed752 fix(package): update fs-extra to version 8.0.0
  • dd0d91f chore(package): update tempy to version 0.3.0
  • 00204d2 chore(package): update nyc to version 14.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of vsce is breaking the build 🚨

The devDependency vsce was updated from 1.64.0 to 1.65.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

vsce is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 12 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Include ".cmd" files as batch type

Windows supports .cmd files as the "new" (since Windows 2000) batch file extension. This file extension is not recognized by TaskExplorer.

Display a flat list of tasks

Having tasks always under a submenu becomes tedious quite quickly. It would be nice if there was an option to show a flat list of tasks to run rather than the tree view currently displayed. Maybe show the full path to the task like npm src/package.json serve. Its a little verbose, but does eliminate 2 repetitive clicks every time open my editor.

Alternatively (or additionally) have an option to start Task Explorer with all folders expanded.

gradle error: Task ' ' not found in root project

gradle error: Task ' ' not found in root project
1\ why select 'build' but exec first task 'admin' in list of ? see Screenshot.
2\ Run gradlew tasks to get a list of available tasks, but 'admin' is not in see Screenshot.

Executing task: ".\gradlew.bat" admin <

FAILURE: Build failed with an exception.

  • What went wrong:
    Task 'admin' not found in root project 'bidolon'.

  • Try:
    Run gradlew tasks to get a list of available tasks
    4
    . Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org
    Screenshot:
    2
    3

An in-range update of jsonc-parser is breaking the build 🚨

The dependency jsonc-parser was updated from 2.0.3 to 2.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jsonc-parser is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

Commits

The new version differs by 9 commits.

  • a367414 2.1.0
  • bbcc6ec prepare release
  • e5f1f8c update changelog & dependencies
  • b9ecc3b Merge pull request #17 from stoplightio/master
  • 85b5249 getTokenStartLine/StartCharacter
  • 7479e45 sort out whitespaces in readme
  • 7971774 add onLineBreak visit function
  • 77ae9d4 Merge pull request #15 from johnspurlock/patch-1
  • d07d83d Fix a few typos in doc comments

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @semantic-release/git is breaking the build 🚨

The devDependency @semantic-release/git was updated from 7.0.16 to 7.0.17.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/git is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v7.0.17

7.0.17 (2019-10-26)

Bug Fixes

  • package: update execa to version 3.2.0 (5132713)
  • require Node.js >=8.16 (7c9eb9a)
Commits

The new version differs by 7 commits.

  • 5132713 fix(package): update execa to version 3.2.0
  • 7c9eb9a fix: require Node.js >=8.16
  • 4b73226 chore(package): update xo to version 0.25.2
  • a317bae ci(node): set node 8 to node 8.3 and add node 12
  • 4cb24c8 chore(package): update clear-module to version 4.0.0
  • 9043edc chore: remove commitizen from our dependencies
  • 55c6df7 chore(package): update commitizen to version 4.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of xml2js is breaking the build 🚨

The dependency xml2js was updated from 0.4.22 to 0.4.23.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

xml2js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

Commits

The new version differs by 5 commits.

  • 8fc5b92 Bump version for next release
  • bb266cf Merge pull request #546 from optoolco/reduce-deps
  • 3c2c99a regenerate lib/parser.js
  • 1adc998 src: Inline util.promisify
  • 882ec6b package: Remove temporary util.promisify dep

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Show full path for a make target

I work on a big project. We have a lot of make targets.
image
It's OK on the side bar. But when I push F1, then Run Task, I see this:
image
instead of common.basic, common.clean, container.basic, ...

BTW: there're some wrong targets (first two)

Keep the new terminal window opened

I wish to have the option to keep the terminal open when I stop the execution of a process.
When I am debugging, I launch bash script then kill them once I saw it does not what I want.

Since the terminal goes away, I need to either keep the script continue to allow me to scroll up to the area I want to see my debug logs OR launch it in a regular terminal without using this extension...

Keep me posted if I am not clear enough.

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v6.2.2

6.2.2 / 2019-10-18

🐛 Fixes

📖 Documentation

Commits

The new version differs by 12 commits.

  • 843a322 6.2.2
  • aec8b02 update CHANGELOG for v6.2.2 [ci skip]
  • 7a8b95a npm audit fixes
  • cebddf2 Improve reporter documentation for mocha in browser. (#4026)
  • 3f7b987 uncaughtException: report more than one exception per test (#4033)
  • ee82d38 modify alt text of image from Backers to Sponsors inside Sponsors section in Readme (#4046)
  • e9c036c special-case parsing of "require" in unparseNodeArgs(); closes #4035 (#4063)
  • 954cf0b Fix HTMLCollection iteration to make unhide function work as expected (#4051)
  • 816dc27 uncaughtException: fix double EVENT_RUN_END events (#4025)
  • 9650d3f add OpenJS Foundation logo to website (#4008)
  • f04b81d Adopt the OpenJSF Code of Conduct (#3971)
  • aca8895 Add link checking to docs build step (#3972)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Add WSL/SSH Remote Support

When doing remote development via ssh or WSL, task explorer does not show tasks and the lists cannot be refreshed without receiving one of the following errors depending on where the refresh button was pressed. The extension has been activated in the remote workspace.

command 'taskExplorerSideBar.refresh' not found
or
command 'taskExplorer.refresh' not found

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.