My experience: This really helps me when working on hosts like vps, wsl and docker environments. With the tight ram limitations I should be able to work productively. Using vscode remotely to the host target it will eat up ram on the host. Because the vscode-server will work to host in full, and here it is the problem. I made this tool so that my environment remains on windows and I just sync my code to host with ssh.
How about debugging?: I rarely use debugging tools on vscode. Just use the console on the host :)
Still connect ssh manually? hmm :( Actually, yes. But I have created a feature ssh direct connect note, for easy to connect ssh just call "ngi-sync direct" and choose where you will connect from your ssh config note.
donny@DESKTOP-T36N2ATMINGW64/d/workspaces_virtualbox$ngi-syncYouarein:D:\workspaces_virtualboxInitializeBootstrapIsDone![ undefined, undefined ]? Direct Access List : (Press<enter>tosubmit)> Running devsync2StartGobetweenEnterVirtualboxEnterdockerMysqldatabaseconsole::OpenConsoledevsync2::OpenDevsync2clean::Gitcleanup:gitadd--renormalize.&&gitreset(Moveupanddowntorevealmorechoices)
Here's why:
Because this <"For my case typescript-javascript|PHP Intelephense as main extensions"> my vscode linting keeps still in use on my local and the code after save will sync to server automatically and compiler run on server will respond to code change.