Getting errors running npm install in the terminal

Under teacher's notes, the instructions are incorrect. We are directed to checkout the "Stage3Video1" branch however it does not contain a package.json file so running "npm install" as instructed gives the error: "Couldn't read dependencies".

You can also checkout particular files from another branch in git like so:

git checkout master -- package.json

Very handy for Huston's courses, so you don't have to always change to a whole other branch for every new video.

As for the install errors, try using sudo npm install -g gulp before you even clone the repo or run npm install.

I tried

npm install -g gulp

I didn't actually try 10 times, after the 3rd time, I just ignored the errors and so far... I'm on the last part of the course and haven't had any problems following along.

So, in my opinion, I wouldn't worry about the errors, because so far there hasn't been a negative impact on my course work.

The error in the teacher notes relies in the order in which the commands are indicated, you have to npm installbefore the checkout, so in order to make it work, yo first have to install the dependencies:

npm install

And then checking out to the specified git tag

git checkout Stage1Video3

If you've already checking out you can return to the master by typing:

git checkout master

=====

This answers is based on what Ryan and Jeff pointed out.

=== UPDATE === If you got this error, it's pretty likely that you tried to install the site before ending de video, if you follow along the video, the teacher shows how to create the package.json file which is the cause of the error

I'm a big fan of Treehouse, and I appreciate and respect Huston's knowledge and jitsu-fu...

But someone needs to revisit the QC on Huston's courses, whether Treehouse has a team of QC people or places the burden on the instructors themselves.

I just finished Express Basics and this kind of nonsense is becoming par for the course with this particular instructor. Teachers' notes out of order, missing repo files, non-existent branches... this should all be ironed out before the course is launched.

Furthermore, in the case that an error of some kind slips through to release, why isn't it fixed after four months, usuallly more?

True Jason, I had errors running the npm install as well, but ignoring them didn't have negative side effects on the rest of the project: everything is running smooth (up to this moment)