![]() The solution is quite simple : in your VSCode launch.json, ensure that your remoteRoot is mapped to the absolute path of your project root, in your guest. You can put almost any value in the remoteRoot field, and if the dugger can't find it, it continues debugging using readonly copies. Visual Studio Code Vagrant VS Visual Studio Code Compare Vagrant vs Visual Studio Code and see what are their differences. Turns out the error is caused by VSCode not being able to map properly to the source files in Vagrant. Create and auto-generate files in Visual Studio Code 10 min. Install and tour Visual Studio Code 10 min. Introduction to Visual Studio Code for web developers 5 min. Code files live on the host filesystem, but are shared with the guest editing happens on the host, execution on the guest. Ubuntu, Debian, Red Hat, Fedora, or SUSE. This first places the box into your global vagrant cache. Visual Studio Code with its Remote - SSH extension can utilize the environment provided by Vagrant, with support for discovering, running and debugging. I do almost all my projects in vagrant, where my VSCode run on my host PC, while my NodeJS runtime lives in a Linux VM. This is just three commands: vagrant box add test- box /path/to/package. ![]() Worst of all, I couldn't fix a bug in the readonly file, so after figuring a solution out I had to fumble the through the mess of open documents to the writeable version. It opened a new copy for every debug run, so after a long session of debugging I would have many files open. Whenever I stepped through a file after hitting a breakpoint, VSCode would open a new read-donly version of the file in a text editor window. For months I've noticed that several of my recent Visual Studio Code projects NodeJS projects were behaving weirdly during debugging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |