You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per Microsoft's Terms of Service, it prohibits any non-Microsoft VS Code from accessing their extension marketplace. Thus many fork of vscode such as VSCodium and code-server are not able to access vscode-leetcode.
open-vsx is an open source alternative to Microsoft's extension marketplace maintained by the Eclipse foundation.
Please consider publishing vscode-leetcode to open-vsx
Contribution
The preferred method of publishing is grabbing a token from Eclipse foundation and then running npx ovsx publish <file>.vsix -p <token> More detailed Instructions for publishing to open-vsx can be found here https://github.com/eclipse/openvsx/wiki/Publishing-Extensions.
Alternatively you can add this repo to https://github.com/open-vsx/publish-extensions extensions.json file. Everyday at 03:03 UTC, it will build and publish for you. The first method is preferred since it displays the official authors as the publishers, while the latter would display a warning that the publisher is not the official authors.
The text was updated successfully, but these errors were encountered:
🚀 Feature Proposal
Publish vscode-leetcode to open-vsx
Motivation
Per Microsoft's Terms of Service, it prohibits any non-Microsoft VS Code from accessing their extension marketplace. Thus many fork of vscode such as VSCodium and code-server are not able to access vscode-leetcode.
open-vsx is an open source alternative to Microsoft's extension marketplace maintained by the Eclipse foundation.
Please consider publishing vscode-leetcode to open-vsx
Contribution
The preferred method of publishing is grabbing a token from Eclipse foundation and then running
npx ovsx publish <file>.vsix -p <token>
More detailed Instructions for publishing to open-vsx can be found here https://github.com/eclipse/openvsx/wiki/Publishing-Extensions.Alternatively you can add this repo to https://github.com/open-vsx/publish-extensions extensions.json file. Everyday at 03:03 UTC, it will build and publish for you. The first method is preferred since it displays the official authors as the publishers, while the latter would display a warning that the publisher is not the official authors.
The text was updated successfully, but these errors were encountered: