Closed ghost closed 13 years ago
Hmm, that's strange, I haven't seen either of those errors before. process.compile() still seems to be in the 0.2.5 documentation without any hint of deprecation. In fact, require("vm") doesn't even seem to be a module in 0.2.5.
As far as the 400 HTTP error, do you know which file it was downloading when it get a 400 error response? Maybe github was having a problem at the time?
I think I found the problem. I'm actually using 2010.11.16, Version 0.3.1 (unstable). I don't know how I got this, I didn't mean to. I must have screwed up when I used npm.
Sorry to bother you. I'll try the latest stable version of node now.
It works fine with 0.2.5. Sorry for the trouble.
Whenever I start nodules.js I get the node error: (node) process.compile should not be used. Use require('vm').runInThisContext instead.
Then all the dependencies load properly.
Then node errors out with ...
node.js:66 throw e; // process.nextTick error, or 'error' event on first tick ^ Error: Error: 400 at /root/nodules/lib/nodules.js:775:9 at notify (/root/nodules/lib/nodules-utils/promise.js:147:27) ... snip ...
This happens on both example and wiki. I'm running Stable: 2010.11.16 node-v0.2.5 and kriszyp-nodules-v0.2.3-3-gcdd6b41.
Any help would be appreciated.