Add ms-vscode.wasm-wasi-core and ms-vscode.webshell

[glebbash]

• I have read the note above about PRs contributing or fixing extensions
• I have tried reaching out to the extension maintainers about publishing this extension to Open VSX (if not, please create an issue in the extension's repo using this template).
• This extension has an OSI-approved OSS license (we don't accept proprietary extensions in this repository)

Description

This PR adds ms-vscode.wasm-wasi-core and ms-vscode.webshell extensions.

Request for the author to add: microsoft/vscode-wasm#152, same situation as with vscode-eslint extension: microsoft/vscode-eslint#1842 (comment)
MIT license: https://github.com/microsoft/vscode-wasm/blob/main/LICENSE

[glebbash]

P.S: not sure if the version bump in the build script will be a problem

[filiptronicek]

Hey @glebbash, thanks a lot for the contribution. It looks like with the current configuration tsc is not super happy. Could you take a look?

Happy to merge when it compiles

[glebbash]

Not sure what was wrong with the previous setup, locally everything worked fine. Updated to custom package scripts.

@filiptronicek can you pls rerun the workflow?

[filiptronicek]

Apparently, typescript still won't budge.

I could reproduce this in a Gitpod workspace using this command:

EXTENSIONS=ms-vscode.wasm-wasi-core,ms-vscode.webshell SKIP_PUBLISH=true node publish-extensions

[glebbash]

Ok, finally figured it out, needed to do npm i in the root of the repository and not in the packages.

[filiptronicek]

All looks good , these should be available on https://open-vsx.org tomorrow on Monday

[glebbash]

Yo @filiptronicek, any ideas why these extensions were not published?

They are present in the last action report but links to them are 404.

[filiptronicek]

@glebbash I think it may have something to do with eclipse/openvsx#945, which should land shortly. Let's see if tomorrow's or Wednesday's CI job picks it up.

[glebbash]

Yay, there are deployed 😀