Scott Moss & Frontend Masters
Thanks for taking the Introduction to Node.js course -- the course has two parts: slides and exercises. The slides describe the exercises in detail. Each exercise have a folder.
Install node with node version manager (NVM). NVM was created by the community and not the Nodejs foundation. However, it is the recommended approach. After installing nvm, use nvm to install the lates version of Nodejs, which at this time is 10
and set it to the default version
nvm install node # node is an alias for the latest version
nvm alias default node
If this fails, or you want to install nodejs from nodejs source, then go here
Important: After installing node, please run npm install i
or npm install
to install the dependencies located in the package.json
file (utilized in future exercises).
- location -
exercises/modules
- commands
- test -
npx jest
- test -
This exercise will have you convert some JavaScript written for the browser, so that it works with node.
- checkout to start branch
- check the README on how to run test (will talk later about that command)
- fix and convert the 3 js files in the exercises/modules/browser to Nodejs JavaScript and place them in exercises/modules/node
- ensure all tests pass by running test command again
- location -
exercises/cli
- commands
- new -
node exercises/cli/index.js new
- list -
node exercises/cli/index.js list
- new -
You'll be creating a CLI program that saves and retrieves contacts from and address book. The program is partially there, however, you must install some remote modules, and use the fileSystem to get some things to work.
- install all remote modules (hint: use npm)
- check the README on how to run your CLI
- Fix the CLI so that the "new" command works by saving contacts to contacts.json
- Fix the CLI so that the "list" command works by listing all contacts and allowing you to select one, the prints out the selected contact
- location -
exercises/api
- commands
- start the server -
node exercises/api/server.js
- start the server -
You'll be refacoring and fixing a simple static asset server. The server uses blocking sync code and crashes whenever a request comes in that is asking for an asset that is not found. Neither of those are desirable. You'll also have to teach the server how to server the assets it has in the assets
folder.
- install all remote modules (hint: use npm)
- check the README on how to run your server
- refactor the sync file reading code to be async with a callback, promise, or async await
- prevent the server from crashing when an assets is not found. Instead, respond with a 404 status code
- create some sort of router logic to handle incoming requests for assets
- location -
exercises/testing
- commands
- start the server -
node exercises/testing/index.js
- test -
npm test
oryarn test
ornpx jest
- start the server -
You have to debug and track down some issues in a small app. Use your logging and inspector to find them. Try and fix them, once you do, write some test to make sure it stays fixed 👌🏾😎💯
- checkout to start branch
- check the README on how to execute this program and run test
- there are 3 bugs, find them and fix them
- write some unit test with Jest to make sure those bugs stay fixed. Refactor the code if you have to
Deploy one of the exercises to heroku (server) or npm (cli)