vscodium-test

The vscode-test npm pkg for vscodium!

Versioning

Upstream version

2.5.2

Why own versioning?

I decided to go with my own semver versioning, beginning with 1.0.0. I tried to find a way to follow microsofts versioning (when writing this, vscode-test latest version is 2.5.2). But I need to be able to fix errors in my fork, which doesnt exist in upstream. And with that demand, I dont see a senseful way to follow upstream versioning. Instead the upstream version will be included in the README for traceability.

Upstream

Microsoft Repo: https://github.com/microsoft/vscode-test/tree/main Microsoft npm package: https://www.npmjs.com/package/@vscode/test-electron?activeTab=readme

Motivation

I use VSCodium because it matches my desire for freedom much more than VSCode does. That comes with some challenges, like the missing Microsoft marketplace. But thats what we have to deal with.

When it came to development of extensions, or more precisly testing of those, a VSCode instance gets shortly opened when using @vscode/test-cli and @vscode/test-electron packages. And I kinda felt forced to use them in order to test properly.

I dont deal with the difficulties mentioned at the beginning just to see a VSCode being opened in the end for trivial testing. Who knows what telemetry it sends during that time.

Therefore my forks vscodium-test-cli and vscodium-test provides the same functionality as upstream, with the only difference VSCodium beeing used.