These JavaScript exercises are intended to complement the JavaScript content on The Odin Project (TOP). They should only be done when instructed during the course of the curriculum.
If you have a suggestion to improve an exercise, an idea for a new exercise, or notice an issue with an exercise, please feel free to open an issue after thoroughly reading our contributing guide.
Fork and clone this repository. To learn how to fork a repository, see the GitHub documentation on how to fork a repo.
Before you start working on any exercises, you should first ensure you have the following installed:
npm --version
in your terminal. If you get back Command 'npm' not found, but can be installed with:
, do not follow the instructions in the terminal to install with apt-get
as this causes permission issues. Instead, go back to the installation lesson and install Node with NVM by following the instructions there.cd javascript-exercises
) and run npm install
. This will install Jest and set up the testing platform based on our preconfigured settings. (Note: if you get warnings that packages are out of date or contain vulnerabilities, you can safely ignore them for these exercises.)Each exercise includes the following:
solutions
directory that contains a solution and the same test file with all of the tests unskipped.To complete an exercise, you will need to go to the exercise directory with cd exerciseName
in the terminal and run npm test exerciseName.spec.js
. This should run the test file and show you the output. When you run a test for the first time, it will fail. This is by design! You must open the exercise file and write the code needed to get the test to pass.
Some of the exercises have test conditions defined in their spec file as test.skip
instead of test
. This is intentional. Once all test
s pass, you will change the next test.skip
to test
and test your code again. You will do this until all conditions are satisfied. All tests must pass at the same time, and you should not have any instances of test.skip
in the spec file when you are finished with an exercise.
Once you successfully finish an exercise, check the solutions
directory within each exercise to compare it with yours.
[!IMPORTANT] Do not submit your solutions to this repo, as any PRs that do so will be closed without merging.
[!NOTE] Due to the way Jest handles failed tests, it may return an exit code of 1 if any tests fail. NPM will interpret this as an error and you may see some
npm ERR!
messages after Jest runs. You can ignore these, or run your test withnpm test exerciseName.spec.js --silent
to supress the errors.
The first exercise, helloWorld
, will walk you through the process in-depth.
To debug functions, you can run the tests in the Visual Studio Code debugger terminal. You can open this by clicking the "Run and Debug" icon on the left or pressing Ctrl + Shift + D, then clicking JavaScript Debug Terminal. You will be able to set breakpoints as you would in the Chrome DevTools debugger. You can run npm test exerciseName.spec.js
to then execute your code up until your breakpoint and step through your code as necessary. NOTE: To take advantage of the debugger, you MUST run the script in the debugger terminal, not the bash or zsh terminal.
To add a new exercise:
npm install
at the root of the javascript-exercises
directory.npm run generate
.After entering an exercise name, a new directory with the necessary files will be created. You will then need to update the README.md
and spec.js
files as well as the files in the solution
directory of the new exercise.