Databases
StackOverflow2013
Postsdbo
POPersistent "Cannot find module" errors when installing juggernaut in OS X and Rails 3
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPersistent "Cannot find module" errors when installing juggernaut in OS X and Rails 3
    text
    copied!<p>I started with a blank install of Lion, installed Xcode 4.1, then followed the instructions at <a href="http://pragmaticstudio.com/blog/2010/9/23/install-rails-ruby-mac" rel="nofollow">http://pragmaticstudio.com/blog/2010/9/23/install-rails-ruby-mac</a> to install rvm, sqlite3, rails and then installed node v0.2.5 and redis v2.0.4. I then tried to install juggernaut: </p> <pre><code>git clone git://github.com/maccman/juggernaut.git --recursive cd juggernaut sudo node server.js </code></pre> <p><strong>After sudo node server.js I get the following error. I have somehow managed to get the same error on 2 separate computers, one with SL 10.6.6 and the other with Lion, clearly I am missing a step somewhere. Also 'optimist' is not the only module that is not found, many other variations of this error e.g cannot find module 'graceful-fs' etc. I have tried installing the modules manually. Please help with this problem.</strong></p> <pre><code>fred:juggernaut fred$ sudo node server.js node.js:134 throw e; // process.nextTick error, or 'error' event on first tick ^ Error: Cannot find module 'optimist' at Function._resolveFilename (module.js:317:11) at Function._load (module.js:262:25) at require (module.js:346:19) at Object.&lt;anonymous&gt; (/Users/fred/Desktop/redis-2.0.4/juggernaut/server.js:2:12) at Module._compile (module.js:402:26) at Object..js (module.js:408:10) at Module.load (module.js:334:31) at Function._load (module.js:293:12) at Array.&lt;anonymous&gt; (module.js:421:10) at EventEmitter._tickCallback (node.js:126:26) fred:juggernaut fred$ </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload