In this lesson you will learn how to support data modification by handling HTTP verbs besides GET.
I agree! I like the project & am learning how routing works but there are some roadblocks that might not be necessary for the learning to keep moving forward.
The comment was 7 months ago so I'll just reiterate... I am constantly having to go to the github repo to see what functions were being built or refactored. It's a good practice in reading the code and seeing what's happening when but a detriment in following the video. WRiting the code with you in the video is not sufficient because there are gaps in what is being built and what is shown. A short heads up on 'so I built this getUser function to fix this problem' would be super helpful. Same thing with the users photos - I didn't clone the repo for this lesson down because I wanted to start from scratch to learn so it would be helpful to have a heads up and say, 'hey, get a collection of photos that you want to use so you can learn to display photos with your user'
The packaged version of nodemon in the repo only watches js by default, but I ran a more recent nodemon (because didn't clone the repo) where nodemon watches .json as well by default, so I had the same issue as Stefan reported of nodemon restarting when .json files where modified or removed.
nodemon index.js --ignore users/ didn't work for me though, nodemon seems to want the --watch flag to watch a file, so:
nodemon --watch index.js. Or
nodemon --ignore users/ or
nodemon --ignore .json would work as well.