-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
RISC-V Support #206766
Comments
@alexdima feel free to reassign to a more relevant person for the remote feature request |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Thanks for the interest, adding support for this architecture to remote requires upstream Node.js to officially support which hasn't happened yet nodejs/build#2876. I will keep this issue open to track. |
🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
ℹ️ Currently, (playwright/chromium is not (yet) available for Linux/RISC-V1. And electron [therefore] also lacks RISC-V support2) Footnotes
|
From what I understand is that there's a lack of upstream support in chromium? |
FYI I maintain a fork1 of electron with riscv64 support, with up-to-date releases published in a separate repo2, which could be used until chromium and electron officially supports riscv64. And VSCodium supports riscv64 client3 and reh build, which could be used with open-remote-ssh4 plugin as a replacement for microsoft's proprietary remote-ssh plugin. Footnotes |
With the rise of popularity for RISC-V processors, and now especially with Scaleway now offering RISC-V instances, it seems that support for RISC-V is becoming more essential. For me and (anecdotally) many others, remote connections to RISC-V machines is becoming the primary way of interacting and developing on the architecture. vim is sufficient, but I would love to remote connect VS Code these machines.
The text was updated successfully, but these errors were encountered: