VS Code tasks fail with error "Cannot read properties of undefined (reading 'shell')"

[apgrucza]

When the extension is enabled, tasks defined in .vscode/tasks.json fail to run. For example:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "echo",
            "type": "shell",
            "command": "echo Hello"
        }
    ]
}

When using the Tasks: Run Task command and selecting the echo task, this error pops up:

Cannot read properties of undefined (reading 'shell')

• Task version: 3.24.0
• Operating System: Windows

[ilkka]

Broken in the same way for me as well, on Linux, with the latest snap version of vs code.

[shalauko]

Same for me on native Windows 10 and in WSL2 (Ubuntu 22.04).
Is there some workaround available?

[polamjag]

Same for me on native macOS (14.2.1 (23C71)) and VS Code 1.85.1 (Universal).

[siberianbot]

Hi! Are there any updates on this?

[3uclid3]

I'm using 'code workspace' with multiple project in it. (multiple taskfiles)

I have more than 1 default build task.
If I'm being ask by vscode to choose, it fails with the error.
If I remove the other tasks and don't have to choose, it work fine.

[MrVermond]

Same here.
So the extension just breaks the vscode tasks feature and is therefore not usable.

[ssbarnea]

@pd93 Apparently vscode-task extension does break native vscode ability to run tasks (unrelated to taskfile). See them documented at https://code.visualstudio.com/docs/editor/tasks#vscode

When this extension is installed we can see the error described by the OP.

[pd93]

Update for all of you very patient people. I've taken a look at this issue several times over the last couple of years since it was opened and I've had a variety of emotions ranging from confusion to anger as I have tried to work out what the issue was. Today I have finally worked it out - and its just as annoying as you might think.

I was fed up with trying to work out what was logically wrong with the extension and instead decided to brute force the problem by slowly removing parts of the extension until the issue went away. Once I found the section that resolved the issue when removed, I created a brand new extension using the Yo generator tool and tried to reproduce the issue. You can see this reproduction here.

To summarise. VSCode extensions have a dedicated "contributes" section of the package.json which defines a variety of things such as commands, views and configuration. In the Task extension, we define our configuration here under the "task" key (so you end up with setting like "task.path": "/path/to/task"). For whatever reason, using this specific key name completely breaks the built-in VSCode tasks feature. I have absolutely no idea why.

To proceed we can:

1. Either accept this quirk of VSCode and put all of our configuration under a new key, such as "go-task" or "taskfile" and accept that anyone with existing configuration will need to migrate it.
2. Raise an issue on the VSCode repository itself to find out if this behavior is intended and what the actual issue is.

• If intended, we ask them to provide better documentation to stop this happening again and see point 1.
• If not intended, we ask them to fix the issue.

Option 2 may take much longer and not result in a solution. However, it will not break users config and we get to keep our settings namespace. I wanted to gather some thoughts here before raising a ticket on the VSCode project.

[andreynering]

@pd93 I suggest openning an issue to see if they respond in reasonable time. If they don't respond in a few days or weeks, we can move the setting namespace.

[pd93]

I suggest openning an issue

microsoft/vscode-discussions#2827