I swear...maybe it's Mountain Lion, I really don't know. I've had my previously-resolved issue with Express not installing globally. It's a work-around, but it works.

However, now after taking a few weeks off due to being too swamped at work to have time to do this, I've gotten back to it and am trying to run the 3 tests on page 23. And every time I attempt to run "npm install make test" I get something like this trash:

Kyles-MacBook-Pro:nockmarket kkerley$ npm install make test
npm WARN package.json nockmarket@0.0.1 No README.md file found!
npm ERR! Error: EACCES, open '/Users/kkerley/.npm/e5e084af-test.lock'
npm ERR! { [Error: EACCES, open '/Users/kkerley/.npm/e5e084af-test.lock']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/Users/kkerley/.npm/e5e084af-test.lock' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Darwin 12.2.1
npm ERR! command "/usr/local/Cellar/node/0.8.8/bin/node" "/usr/local/bin/npm" "install" "make" "test"
npm ERR! cwd /Users/kkerley/Documents/www/nockmarket
npm ERR! node -v v0.8.8
npm ERR! npm -v 1.1.59
npm ERR! path /Users/kkerley/.npm/e5e084af-test.lock
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, open '/Users/kkerley/.npm/e5e084af-test.lock'
npm ERR! Error: EACCES, open 'npm-debug.log'
npm ERR! { [Error: EACCES, open 'npm-debug.log'] errno: 3, code: 'EACCES', path: 'npm-debug.log' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Darwin 12.2.1
npm ERR! command "/usr/local/Cellar/node/0.8.8/bin/node" "/usr/local/bin/npm" "install" "make" "test"
npm ERR! cwd /Users/kkerley/Documents/www/nockmarket
npm ERR! node -v v0.8.8
npm ERR! npm -v 1.1.59
npm ERR! path npm-debug.log
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, open 'npm-debug.log'
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/kkerley/Documents/www/nockmarket/npm-debug.log
npm ERR! not ok code 0


And if I run it as sudo, I get something similar but not quite as obscenely long.

Kyles-MacBook-Pro:nockmarket kkerley$ sudo npm install make test
Password:
npm WARN package.json nockmarket@0.0.1 No README.md file found!
npm http GET http://reigstry.npm.org/npm/make
npm http GET http://reigstry.npm.org/npm/test
npm http GET http://reigstry.npm.org/npm/make
npm http GET http://reigstry.npm.org/npm/test
npm http GET http://reigstry.npm.org/npm/test
npm http GET http://reigstry.npm.org/npm/make
npm ERR! Error: getaddrinfo ENOENT
npm ERR! at errnoException (dns.js:31:11)
npm ERR! at Object.onanswer [as oncomplete] (dns.js:123:16)
npm ERR! If you need help, you may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-@googlegroups.com>

npm ERR! System Darwin 12.2.1
npm ERR! command "/usr/local/Cellar/node/0.8.8/bin/node" "/usr/local/bin/npm" "install" "make" "test"
npm ERR! cwd /Users/kkerley/Documents/www/nockmarket
npm ERR! node -v v0.8.8
npm ERR! npm -v 1.1.59
npm ERR! syscall getaddrinfo
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/kkerley/Documents/www/nockmarket/npm-debug.log
npm ERR! not ok code 0
Kyles-MacBook-Pro:nockmarket kkerley$


I Googled a bit and came across a Stack Overflow post (http://stackoverflow.com/questions/1...ng-npm-install) that said the NPM registry is down/not working and it offered 3 fixes. I've tried all 3 of framp's suggestions and the result is the same. I really want to learn Node.js, but it seems like doing so is a full-time job and requires all sorts of babying and fussing that just really isn't worth it. I'm following the book to a T. I'm following the troubleshooting directions I find online after following the book results in errors to a T. And it's still not working. It shouldn't be the hard and quite honestly, I don't care anymore. It feels like Rails back in the 1.2 days. But worse.

I guess there's not really much point to this post other than to vent but yeah...I'm tired of sitting here screaming at my computer, feeling like a total idiot when it really shouldn't be this difficult.

Hope the rest of you have been able to get it working and are now all established Node.js programmers. Apparently, this just isn't for me.