Cannot get started running

[furtivefelon]

Hey all,

I cannot get started with this thing, i have successfully install wheat, connect, cluster, and i also added .listen(3000) to the end of app.js (before ;), i get the following error:
jason@ubuntu howtonode.org % node app.js

node.js:178
throw e; // process.nextTick error, or 'error' event on first tick
^
TypeError: Object function createServer() {
if ('object' == typeof arguments[0]) {
return new HTTPSServer(arguments[0], Array.prototype.slice.call(arguments, 1));
} else {
return new HTTPServer(Array.prototype.slice.call(arguments));
}
} has no method 'conditionalGet'
at Object. (/home/jason/howtonode.org/app.js:6:11)
at Module._compile (module.js:404:26)
at Object..js (module.js:410:10)
at Module.load (module.js:336:31)
at Function._load (module.js:297:12)
at Array. (module.js:423:10)
at EventEmitter._tickCallback (node.js:170:26)

If anyone have any idea of what is going on it would be much appreciated if you can enlighten me, thanks a lot!

Jason

[mattkatz]

I looked into this - it seems that 'wheat' which the blog runs on, depends on 'connect'. I did npm install wheat, but it didn't install connect.

Then I did npm install connect and we get connect. This got me to the same point you are at.

When I look at the repo for 'connect' https://github.com/senchalabs/connect I see that conditionalGet was removed - and it looks like this explicitly exports conditionalGet in the app.js.

So if we can figure out which version of connect supported conditionalGet we could probably npm install connect@version and get something working. I haven't figured out which version we should install.

[mattkatz]

ok, it SEEMS like npm install connect@0.5.10 will get it a little farther. eventually I sort of get things running, but can't access anything when trying to run from cloud9.

[furtivefelon]

So did you get the same sort of error as me? Or did you get yours working?

[mattkatz]

I got it just a bit farther than you. I'm just trying this out as a fun way to learn node on cloud9ide - and I got it to a state where I didn't get any errors, but I also didn't get any actual output either.

[mchelen]

npm install connect@0.5.10 worked for me when running with Spark

[amaurer]

I was able to get it started with connect@0.5.10 as well without using spark.

Any chance of fixing this to use the latest version of connect instead of making people dig for answers (frustrated but ok now)