language-tools
vscode-remote-release
language-tools | vscode-remote-release | |
---|---|---|
1 | 35 | |
249 | 3,489 | |
1.2% | 2.0% | |
10.0 | 3.0 | |
5 days ago | 10 days ago | |
TypeScript | ||
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
language-tools
-
Iām Switching from VS Code to vs Codium
It might be worth contacting these extensions' creators. If you already have the `.vsix` file for the VSCode marketplace, publishing to open-vsix is really super simple (create an account once, get a token, add a few lines to your publish script, e.g. https://github.com/prisma/language-tools/blob/94e4cd612d03ef...). Some just do not know about it.
vscode-remote-release
-
Code tunnel to local machine directly (without Azure)
It would be great, if people interested in this feature/having similar problems would consider pushing the following issue: https://github.com/microsoft/vscode-remote-release/issues/8373
-
xdg-open shim for remote ssh to headless server (VSCode)
The other option may require that you add the Remote X11 extension to VSCode (Unless Microsoft has undone the damage they did to their OpenSSH client in the last few years in which case you could just enable X11 forwarding in your ssh options) if you're trying to execute everything from VSCode, and you would have to have a suitable browser or viewer installed on the remote server along with the xdg-utils package (or whatever contains xdg-open if you're not running Debian).
- Remote VSCode over SSH crashes EC2 instance
-
How to execute a file that sets up the environment that is needed for intelisense to work properly?
Take a look at this: https://github.com/microsoft/vscode-remote-release/issues/6375
-
Host pty got disconnected
If it's "The connection to the terminal's pty host process is unresponsive, the terminals may stop working", apparently it's an old problem: https://github.com/microsoft/vscode-remote-release/issues/7964
- Requesting upvotes for vs code dev container postStartCommand issue
-
A step to step guide to set up Dev Container
VSCode with Remote-Container extension installed.
-
SSH on Raspberry Pi using VS Code
Possibly related github issue?
-
Connect from Visual Studio Code to FreeBSD
This might be it.
-
A way to connect to computers via SSH without VPN
Hello! I came across this Github issue that I think would be helpful for remote workers. It's about the possibility to connect to an existing tunnel by using the terminal of OS instead of VSCode UI. This would allow us to use tunnels as a full SSH replacement in scenarios where SSH itself isn't possible. If you think this would be helpful, please upvote the issue here: https://github.com/microsoft/vscode-remote-release/issues/8238
What are some alternatives?
vscode-intelephense - PHP intellisense for Visual Studio Code
pylance-release - Documentation and issues for Pylance
javavscode - Java platform support for Visual Studio Code for full featured Java development (edit-compile-debug & test cycle)
rpm-ostree - āš¦ Hybrid image/package system with atomic upgrades and package layering
intellij-rust - Rust plugin for the IntelliJ Platform
patchelf - A small utility to modify the dynamic linker and RPATH of ELF executables
vscode-remote-oss - Remote development for OSS Builds of VSCode like VSCodium
god-mode - Minor mode for God-like command entering
Visual Studio Code - Visual Studio Code
pyright - Static Type Checker for Python
code-yew-server - An extension that provides some language features for Yew's html macro syntax in Rust
ostree - Operating system and container binary deployment and upgrades