https://github.com/nikclayton/edabit-javascript-challenges
Javascript challenges forked from Edabit
https://github.com/nikclayton/edabit-javascript-challenges
challenge edabit javascript kata
Last synced: 24 days ago
JSON representation
Javascript challenges forked from Edabit
- Host: GitHub
- URL: https://github.com/nikclayton/edabit-javascript-challenges
- Owner: nikclayton
- License: mit
- Created: 2019-02-23T16:32:31.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2021-04-27T07:01:36.000Z (about 4 years ago)
- Last Synced: 2023-03-11T23:26:06.965Z (about 2 years ago)
- Topics: challenge, edabit, javascript, kata
- Language: JavaScript
- Size: 1.18 MB
- Stars: 20
- Watchers: 1
- Forks: 20
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# edabit-javascript-challenges
Javascript challenges forked from Edabit.
Now you can do the challenges locally, using whichever IDE you prefer.
## Install Node / NPM
You will need to install NodeJS from https://nodejs.org and ensure that
you can run the `npm` command by running
``` shell
npm version
```
and verifying that you see the NPM version, and not an error.
## Trying a challenge
To try a challenge:
- Change in to to the directory containing the challenge.
- Run `npm install` to install the necessary dependencies.
- Read `README.md` for a description of the problem.
- Read the tests in `code.spec.js` to get a better understanding of
exactly what parameters the code you will write should take, and
the values your code should return.
- Run the tests wth `npm test`. They should fail.
- Edit the function in `code.js`. When you think you have written the
code correctly re-run the tests (`npm test`) to check. If they pass,
great. If not, try and understand the failure, and edit your code to
fix the problem. Then re-run the tests.
If you get stuck on a challenge, move on and try and different one for
a bit. This gives your mind the chance to subconsciously think about
the problem, and you can come back later and try and solve it again.