Firstly, go and install VSCode for windows .
Windows is a very different environment to use the terminal on than Linux based systems (which evolved from UNIX , as opposed to windows which evolved from DOS ). Unix based systems are more commonplace in research and industry, so instead of using the windows terminals we encourage you to use the linux terminals inside of windows. To set this up, we'll be creating a Linux system inside Windows using a tool called Windows Subsystem for Linux (WSL) .
wsl --install
. You might need to wait a few minutes for it to complete.
Enter a new UNIX username . This name should be entirely lowercase with no whitespace. Just use your first name.
uname
command). The first thing you should do is update your system by running <code>sudo apt update sudo apt upgrade. If possible, you should memorise and run this command every few weeks to make sure your Linux system stays up-to-date.</li><li>The next thing we need to do is link WSL to VS Code. Open VS Code from the Windows start menu, then go to the extensions panel ( <em>4 boxes </em>icon on the left-hand side).</li><li>Search for and install the WSL extension. It tells VS Code how to communicate with the Windows Subsystem for Linux, which allows you to use VS Code on Windows with the back-end running on Linux.</li><li>Once the extension has installed, you should see a “two arrows” button in the bottom-left corner of your VS Code window. Click it and choose to <code>Connect to WSL. Wait for it to download and install the backend.
Ctrl + `
(control back-tick). You should see that it connects to WSL's terminal automatically.</li><li>Finally, make sure Git is installed by running <strong>git --version </strong>in your terminal. If you see something like <strong>git version 2.40.1 </strong>, it is installed correctly. If you get a <strong>git: command </strong>not found error, you should install Git by running <code>sudo apt install git . Congratulations, you've successfully set up WSL and git!
nvm install 20
, which will download and install the correct version of NodeJS. After it completes, run the <code> node --version command to check if it installed correctly. You should see something like "v20.12.2" as the output.
Resource created Tuesday 13 August 2024, 01:02:02 PM, last modified Tuesday 27 August 2024, 11:00:42 AM.