Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/frontendmasters/intro-node-js

[Course] Code for Introduction to Node.js
https://github.com/frontendmasters/intro-node-js

exercises node nodejs

Last synced: 3 days ago
JSON representation

[Course] Code for Introduction to Node.js

Awesome Lists containing this project

README 

        
> [!NOTE]

> This repo is from an archived version of the course. Watch the latest version of the course on [frontendmasters.com](https://frontendmasters.com/courses/node-js-v3/).



# Intro to Nodejs

> Scott Moss & Frontend Masters

- [Resources](#resources)

- [Course](#course)

- [Exercises](#exercises)

  - [Installing Node](#installing-node)

  - [Modules (node vs browser)](#modules-node-vs-browser)

  - [CLI (npm)](#cli-npm)

  - [API (async code)](#api-async-code)

  - [Debugging & Testing](#debugging--testing)

  - [Sharing and Deploying](#sharing-and-deploying)



## Resources

* [Slides](https://slides.com/scotups/deck/fullscreen)

* [Nodejs](https://nodejs.org/en/)

* [NVM](https://github.com/creationix/nvm)

* [Heroku](https://heroku.com)

* [NPM](https://www.npmjs.com/)



## Course

Thanks for taking the [Introduction to Node.js course](https://frontendmasters.com/courses/node-js/) -- the course has two parts: slides and exercises. The slides describe the exercises in detail. Each exercise have a folder.



## Exercises



### Installing Node

Install node with [node version manager (NVM)](https://github.com/creationix/nvm#installation). 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

```bash

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](https://nodejs.org/en/)



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).

### Modules (node vs browser)

* location - `exercises/modules`

* commands

  * test - `npx jest`



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

### CLI (npm)

* location - `exercises/cli`

* commands

  * new - `node exercises/cli/index.js new`

  * list - `node exercises/cli/index.js list`



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

### API (async code)

* location - `exercises/api`

* commands

  * start the server - `node exercises/api/server.js`



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

### Debugging & Testing

* location - `exercises/testing`

* commands

  * start the server - `node exercises/testing/index.js`

  * test - `npm test` or `yarn test` or `npx jest`



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

### Sharing and Deploying

Deploy one of the exercises to heroku (server) or npm (cli)