Add extension to Open VSX Registry

[jharmer95]

What version of this package are you using?
N/A

What problem do you want to solve?
StandardJS is only available on the Microsoft VSCode Marketplace. This prevents it from being used by open-source versions of VSCode (i.e. VSCodium, Theia).

What do you think is the correct solution to this problem?
Also publish the extension to Open VSX, guide available here

Are you willing to submit a pull request to implement this change?
N/A

[EchedelleLR]

I am interested too

[EchedelleLR]

As pointed by other users who requested it for their favourite extensions "It is unclear if it's legal to use the official Microsoft extension marketplace on VS Code forks, see here" so would be more beneficial in general to have it on Open VSX.

[theoludwig]

Apparently, the extension is published to Open VSX Registry by @markwylde
Link : https://open-vsx.org/extension/markwylde/vscode-standardjs

[markwylde]

Apparently, the extension is published to Open VSX Registry by @markwylde
Link : https://open-vsx.org/extension/markwylde/vscode-standardjs

Yeah Divlo, I have published it temporarily, but would love to delete it in favour of an official one from the standard team.

[markwylde]

Updated to 1.4.0

Let me know if there's any problems.

[feross]

Cool, happy to publish an official version to Open VSX if it's not too much extra work. It looks like they're changing the publishing process in December 2020 so I want to wait until that's finished before figuring out the process. https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

[markwylde]

@feross openvsx has now been transferred to eclipse and the new process is in effect. I've just gone through the pairing process, and it worked.

So if you do have a few minutes free one day, you should be able to register and publish the extension. If you need any help, please feel free to reach out.

Make sure to "claim" [1] the standard namespace, so no one else can publish under the name "standard".

Also once it's published, I'll remove the version I've uploaded to avoid any confusion.

1. https://github.com/EclipseFdn/open-vsx.org#claiming-namespace-ownership

[theoludwig]

I guess, we could have some Continuous Deployment (CD) for automatically publishing to the 2 marketplaces automatically when we create a new release ("tag") on GitHub.

Also the branch on master isn't working for standard engine since #140, because the changes were indeed working for standard but it wasn't for ts-standard that needed a tsconfig.json file to work, so I tried a workaround in #139, and add a small condition to only do the thing with standard engine, but it seems like it brokes everything (my bad).
So in the #142 PR, I revert the #140 PR and now everything is working as expected for every engines but obviously, we don't solve the #140 PR.

We could first merge #142, and then release v1.5.0 on both marketplace. 👍

EDIT: in #142 PR, I implemented automated deployment to deploy to both VSCode Marketplace and Open VSX automatically.

[jharmer95]

Awesome, thanks!

[theoludwig]

Thanks for your help! @markwylde
Could you please, remove your version of the extension to open-vsx registry, thanks!
The extension is now available here: https://open-vsx.org/extension/standard/vscode-standard

[markwylde]

I've requested the removal now. Thanks @divlo