...
Intention | Command |
---|---|
Comment out block of code | ctrl+K+C |
Remove comment around a block | ctrl+K+U |
Working with Node.js Web Application
Begin by using the Run button on the left of VSC.
Select the run button at the top/ Add Configuration...
From the dropdown search for "Node.js: Attach to Process"
Code Block | ||||
---|---|---|---|---|
| ||||
{
"name": "Attach by Process ID",
"processId": "${command:PickProcess}",
"request": "attach",
"skipFiles": [
"<node_internals>/**"
],
"type": "pwa-node"
} |
Now attach VSC to it using the new launch configuration you created above - as you can see here our app is the first in the list
Refresh the browser, the breakpoints should be reached
Using SSH from VSC
Info | ||
---|---|---|
| ||
These instructions assume that you have created a VM with a public key already assigned to it, and you have the public/private keys available to you on your host. AWS creates and assigns the keys for you, GCP does not, you will need to USE ssh-keygen to create the keys and then assign the public when you create the VM. I'm not sure about Azure |
- Install SSH - Remote tools
- Create a config file that contains the connection details, the file is called config with no file extension and should be placed in the /Users/<username>/.ssh folder
Code Block Host sels-mc HostName 130.211.75.156 IdentityFile ~/.ssh/gcp-key User selvy
The indentation is important
- Open the Remote connection
- You might be prompted for OS version, select what's appropriate
- A new VSC window appears, select the file explorer button
- Select Open Folder
- Your home folder on the remote VM should be listed, select OK
- The view should update to show the files in your home folder
- Opening a terminal window in VSC will shell into the terminal on the remote VM that your VSC instance is connected