Provided tasks are not available when VSIX extension targets web

[thegecko]

Does this issue occur when all extensions are disabled?:No

• VS Code Version: VS Code Web 1.70.2
• OS Version: Chrome (Mac OS)

Issue:

Although tasks are not currently officially supported in VS Code web, they do work for PseudoTerminal-based task providers.

However, the packaging method of the VSIX extension effects whether these work or not.

In our testing, tasks in VS Code Web work correctly when:

• Sideloaded from localhost into vscode.dev
• Run locally using @vscode/test-web
• Packaged as a universal extension (without the --target flag) and published on the marketplace

However tasks do not work when the VSIX is packaged explicitly for the web using:

vsce package --target web

In this case, the tasks.json is successfully parsed without squiggles, but the following error appears when executing the task:

I believe there is an intent to increase tasks support in VS Code Web so would be keen to see a fix for this issue.

Steps to Reproduce:

1. Build this example extension
2. Package it using vsce package and observe it works as expected in VSCode Web installed from the marketplace
3. Package it using vsce package --target web and observe it does not work as expected in VSCode Web installed from the marketplace

It's not clear whether this issue is in VS Code vsce or in the marketplace/hosting, but my guess is there is something which blocks tasks when the extension is explicitly built for the web.

[meganrogge]

I think this is working as expected. If an extension contributes tasks, the expectation would be that it's packaged for not only the web, as tasks are not really designed to run there.

[meganrogge]

I also have not seen other reports of this, so don't imagine we will get to investigating it any time soon. Thanks for the issue and for your understanding.

[thegecko]

If an extension contributes tasks, the expectation would be that it's packaged for not only the web

We do package this for both the desktop and for the web.

We use this flag to create a specific package for the web which doesn't include some binaries so that the web version isn't over inflated.