refactor: change publisher to expo
#174
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exciting times ahead for the vscode plugin!
Todos
Verify the Expo publisher on vscode marketplace
→
Pending infra deployment→ Done!
Claim the open-vsx.org
expo
publisher→ See Claiming namespace expo EclipseFdn/open-vsx.org#1831
→ Thanks to @kineticsquid, this is now done: https://open-vsx.org/extension/expo/vscode-expo
Contact Microsoft for extension transfer
→
Reached out, awaiting replyWhile the OpenVSX community is awesome in terms of support, and transferability, @microsoft doesn't allow this. I'll deprecate
byCedric.expo-tools
, after we publishedexpo.expo-tools
on the vscode marketplace.It's an absolute bummer, since we lose all reviews and downloads so far, but it is what it is.