Failed to load resource about slides HOT 5 CLOSED

Hey @StewartNoyce. Were there any errors from npm install? Or from the bower install? I just verified that it works for me on a fresh clone using the steps in the README, so maybe something weird happened in your particular case. Also, what OS and what version of npm & node?

from slides.

Thanks, it could very well be something in my environment. I just ran through the same exercise again on a different system as a quick test. The test system was a Mac Mini Intel Core 2 Duo running OS X 10.6.8 (Snow Leopard) with node v0.8.16 and npm v1.1.69. It gave me essentially the same result.

There were no errors in the npm or bower installs, just this warning:

npm WARN prefer global [email protected] should be installed with -g

Everything on this list shows up in the node_modules folder underneath bower. There is no bower_components folder, though.

[email protected] node_modules/bower
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected])

from slides.

It sounds like bower install may not be executing (It's supposed to be run as a part of npm install--see the prepublish task in package.json). Can you tell if it's being run or not? If it is being executed, then perhaps it is failing for some reason. If it's not, then that's certainly the problem, but I don't really know why it would be executed.

You could try running it manually to see if that gets things working for you. You can run the locally installed bower (from the slides dir):

./node_modules/.bin/bower install

Or, you can install bower globally yourself and run it:

npm install -g bower
bower install (again, from the slides dir)

I typically prefer using a local copy of bower (even though it wants to be installed globally, hence the warning during npm install). That allows for a bit more insulation against potential breaking changes in bower (they had a few before 1.0).

Let me know if you're able to get it working by manually running bower install.

from slides.

A local bower install solved the problem. I used this path from the /slides directory:

'node_modules/bower/bin/bower install'.

Thanks.

from slides.

Glad that got it working for you. It still seems very odd that bower install was not being run by npm install ... maybe the prepublish npm hook worked differently in previous versions of npm (I'm using 1.3.5).

I'll close this issue, since you have a workable solution, and if someone else reports a similar problem, I'll look into it more deeply. Thanks!

from slides.