VS Code built-in extensions are published nightly from now on

Here is the job: https://github.com/theia-ide/vscode-builtin-extensions/actions?query=workflow%3Apublish-vscode-built-in-extensions

  • To see list of all published extensions, open the latest successful job, then Deploy Extension and scroll down.

  • To get a link for a concrete extension, for example Git:

> npm info @theia/vscode-builtin-git@next dist.tarball
https://registry.npmjs.org/@theia/vscode-builtin-git/-/vscode-builtin-git-0.3.0-next.db32534bf1.tgz

There is no guarantee that they work though, some of them can rely on new or proposed APIs. Please file issues. For stable use latest tag as before. If the job is failing, let us know

[original thread by Anton Kosyakov]

Actually, not sure whether someone can see the job state without belonging to Theia org or GitHub account. Maybe we are better to add a badge to main Theia repo that we also see its state constantly? @svenefftinge @marc-dumais

We could actually set up vscode-api-tests to run automatically in vscode-builtin-extensions as well against latest build-in extensions.

here is a PR to add the badge: https://github.com/eclipse-theia/theia/pull/6577

[Anatoliy Bazko]

What are the benefits of publishing in comparison with https://www.npmjs.com/package/@theia/vscode-builtin-git for instance?

It publishes against latest commit from VS Code, i.e. https://www.npmjs.com/package/@theia/vscode-builtin-git/v/0.3.0-next.782f1592de corresponds to https://github.com/microsoft/vscode/commit/782f1592de7733cfbc6675300371ae8fd88bdd57 (current master state of VS Code on the moment of writing this message)