Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode Extension: Publish a no-server version without bundled binary #18578

Open
darkyzhou opened this issue Dec 1, 2024 · 5 comments
Open
Labels
A-infra CI and workflow issues A-vscode vscode plugin issues C-feature Category: feature request

Comments

@darkyzhou
Copy link

darkyzhou commented Dec 1, 2024

I'd like to suggest publishing an additional extension variant without the bundled rust-analyzer binary, for two main reasons:

  1. Reduce download size and time
  2. Enable support for architectures not officially supported by VSCode (e.g., RISC-V and Loong64 on VSCodium)

Currently, users on these alternative architectures cannot install the extension due to architecture restrictions, even if they have rust-analyzer installed on their system manually.

Would it be possible to publish such a "no-server" variant alongside the current extension?

@darkyzhou darkyzhou added the C-feature Category: feature request label Dec 1, 2024
@lnicola
Copy link
Member

lnicola commented Dec 1, 2024

@darkyzhou
Copy link
Author

I think there are a few differences:

  1. The .vsix requires manual download and installation, which is less user-friendly than having it available in the extension registry
  2. I'm not sure whether auto-updating will work correctly with the manually installed no-server variant

P.S. For "publishing" I actually meant publishing to Open VSX registry, which VSCodium is configured to use by default

@lnicola
Copy link
Member

lnicola commented Dec 1, 2024

Does OpenVSX support Loong64? Extensions have to specify their platform, which is how the marketplace knows which version to send. Last time I checked, only x86, x64 and arm were available.

@lnicola
Copy link
Member

lnicola commented Dec 1, 2024

Oh, I see, you want a different extension that's marked as portable. That would technically work, but it's more involved because of.. bureaucratic reasons.

@darkyzhou
Copy link
Author

Yes, that's exactly my concern...

While having two separate extensions does feel a bit awkward, I was thinking maybe just publishing the no-server variant to Open VSX would be sufficient.

@lnicola lnicola added A-vscode vscode plugin issues A-infra CI and workflow issues labels Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-infra CI and workflow issues A-vscode vscode plugin issues C-feature Category: feature request
Projects
None yet
Development

No branches or pull requests

2 participants