Professional Documents
Culture Documents
You can download and install VSCodelaunch[external] for your operating system. Here are a
few configuration tips once you have it installed:
Trust a folder: Create a folder where you will keep your work for this class. Open the
folder in VSCode (e.g. by clicking on the top sidebar icon and then clicking Open
Folder), and when prompted, choose to trust its contents.
Install the ESLint extension: Click on Extensions along the left and search for ESLint.
This will flag linter issues (often stylistic, but also many that may suggest problems with
functionality) in the editor so you don't have to run the linter separately.
We recommend that you disable JavaScript › Suggest: Auto Imports. VSCode has
some trouble understanding which libraries are usable and will often suggest adding
imports that lead to errors.
o To find this option, go to File -> Preferences -> Settings, and search for it.
Change Editor: Tab Size to 2. This is the value we will use in our starter code and the
linter. If you want to use a different tab size, you will have to update the linter
configuration file to avoid errors (we will discuss this later when we post assignment 1).
Adjust autocomplete and suggestion settings to your liking. Some folks find it helpful,
while others find it gets in the way. You can search for "auto close" and "suggest" to see
the options.
Take note of Files: Hot Exit. By default, when you close VSCode, it will remember the
changes you have made to open files so you will have them again when you reopen it, but
it will not actually save the changes back to the file. This can be confusing because, even
though you don't have any VSCode windows open, the actual files may not have your
most recent edits. If you like this behavior (e.g. because you open and close your editor a
lot and don't want to deal with save prompts all the time), that's fine; just make sure you
hit Save.
7. Link the newly installed version of node by running brew link --force --overwrite
node@18.
8. You'll also likely need to grant Terminal "Full DIsk Access", or else programs you run
from the Terminal won't be able to create files. To do this, System Settings (or System
Preferences depending on your macOS version), Privacy and Security, Full Disk Access,
and check the box for Terminal.
9. Follow the steps to verify your setup.
3. $ node -v
v18.15.0
Note: If you have a newer version of Node (e.g. 19), you should be okay. We recommend
Node 18 based on its longer support window.
4. Verify that NPM is installed by running the command npm -v. The specific NPM version
should not matter. For example:
5. $ npm -v
8.19.2
6. If both of the above commands print out a number and no error messages, you should be
all set! It's okay if the numbers you get don't match these exactly.