cannot generate new app w/ geddy v0.2.0 #67

Closed
ne0zen opened this Issue Nov 26, 2011 · 3 comments

2 participants

@ne0zen

ran into errors trying to generate a new app using geddy v0.2.0
clean Mac OS X lion, NodeJS v0.4.7 (version heroku provides) installed via nvm (https://github.com/creationix/nvm)

rheflin@saffron:~ $ npm list -g
/Users/rheflin/.nvm/v0.4.7/lib
└─┬ npm@1.0.106 
  ├── abbrev@1.0.3 
  ├── graceful-fs@1.0.1 
  ├── ini@1.0.1 
  ├─┬ minimatch@0.0.4 
  │ └── lru-cache@1.0.4 
  ├── node-uuid@1.2.0 
  ├── nopt@1.0.10 
  ├── proto-list@1.0.0 
  ├── request@2.1.1 
  ├── rimraf@1.0.8 
  ├── semver@1.0.11 
  ├── slide@1.1.3 
  └── which@1.0.2 
  • Install Latest geddy
rheflin@saffron:~ $ npm install -g geddy
/Users/rheflin/.nvm/v0.4.7/bin/geddy -> /Users/rheflin/.nvm/v0.4.7/lib/node_modules/geddy/bin/cli.js
jake@0.1.20 /Users/rheflin/.nvm/v0.4.7/lib/node_modules/geddy/node_modules/jake 
geddy@0.2.0 /Users/rheflin/.nvm/v0.4.7/lib/node_modules/geddy 
  • try and generate an app
rheflin@saffron:~ $ geddy app bytor

node.js:134
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
Error: Command failed: /bin/sh: jake: command not found

    at ChildProcess.exithandler (child_process.js:102:15)
    at ChildProcess.emit (events.js:67:17)
    at Socket.<anonymous> (child_process.js:172:12)
    at Socket.emit (events.js:64:17)
    at Array.<anonymous> (net.js:829:12)
    at EventEmitter._tickCallback (node.js:126:26)
  • so, it can't find jake... no biggie. Installed jake globally via npm
rheflin@saffron:~ $ npm install -g jake
/Users/rheflin/.nvm/v0.4.7/bin/jake -> /Users/rheflin/.nvm/v0.4.7/lib/node_modules/jake/bin/cli.js
jake@0.1.20 /Users/rheflin/.nvm/v0.4.7/lib/node_modules/jake 
  • but still can't generate an app.
rheflin@saffron:~ $ geddy app bytor

/Users/rheflin/.nvm/v0.4.7/lib/node_modules/geddy/bin/cli.js:130
        throw err;
        ^
Error: Command failed: jake aborted.
TypeError: Object [object Object] has no method 'exec'
    at [object Object].action (/Users/rheflin/.nvm/v0.4.7/lib/node_modules/geddy/Jakefile:77:10)
    at [object Object].runNextTask (/Users/rheflin/.nvm/v0.4.7/lib/node_modules/jake/lib/jake.js:351:27)
    at [object Object].runTask (/Users/rheflin/.nvm/v0.4.7/lib/node_modules/jake/lib/jake.js:196:10)
    at Object.<anonymous> (/Users/rheflin/.nvm/v0.4.7/lib/node_modules/jake/bin/cli.js:73:10)
    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.<anonymous> (module.js:423:10)
    at EventEmitter._tickCallback (node.js:126:26)

    at ChildProcess.exithandler (child_process.js:102:15)
    at ChildProcess.emit (events.js:67:17)
    at ChildProcess.onexit (child_process.js:192:12)

hope this helps.

@mde

Ah, I guess when you declare a package as a dependency, NPM assumes a local installation? In any case, the Geddy generation-scripts depended on some newer Jake features that were not in the latest release. I've pushed a new release, so things should work if you update Jake via NPM -- I think you have to make sure you updates it globally with the -g flag as well. Let me know if this fixes you up. Thanks a lot!

@ne0zen

yep. worked great.

@mde

Excellent, thanks. :)

@mde mde closed this Nov 28, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment