Error Command Failed /bin/sh Jake Command Not Found
Contents |
Sign in Pricing Blog Support Search GitHub This repository grunt command not found mac Watch 97 Star 1,909 Fork 271 geddy/geddy Code Issues
Grunt Command Not Found Ubuntu
137 Pull requests 10 Projects 0 Wiki Pulse Graphs New issue Cannot generate new
Grunt Command Not Found Windows
project on Mac OS #119 Closed Marak opened this Issue Apr 12, 2012 · 1 comment Projects None yet Labels None
Command Not Found Bash Mac
yet Milestone No milestone Assignees No one assigned 1 participant Marak commented Apr 12, 2012 npm 1.1.16 node 0.6.15 Trying to perform command geddy app foo as directed in README to generate project. sudo npm install geddy -g npm http GET https://registry.npmjs.org/geddy npm bash: grunt: command not found http 304 https://registry.npmjs.org/geddy npm http GET https://registry.npmjs.org/jake npm http 304 https://registry.npmjs.org/jake /usr/local/bin/geddy -> /usr/local/lib/node_modules/geddy/bin/cli.js geddy@0.3.21 /usr/local/lib/node_modules/geddy └── jake@0.2.33 $ sudo geddy app foo node.js:201 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:282:15) at ChildProcess.emit (events.js:70:17) at maybeExit (child_process.js:360:16) at Socket.
Sign in Pricing Blog Support Search GitHub This repository Watch 97 Star 1,909 Fork 271 geddy/geddy Code Issues 137 Pull requests 10 Projects 0 grunt command not found windows 7 Wiki Pulse Graphs New issue "geddy app abc" fails on fresh geddy bash command not found linux v0.4.7 #212 Closed mistermojo opened this Issue Oct 5, 2012 · 12 comments Projects None yet Labels command-not-found zsh None yet Milestone No milestone Assignees No one assigned 5 participants mistermojo commented Oct 5, 2012 I did not install geddy before so, I ran: sudo npm install https://github.com/geddy/geddy/issues/119 -g geddy ... geddy@0.4.7 /usr/lib/node_modules/geddy ├── utilities@0.0.13 ├── barista@0.0.7 (inflection@1.2.3) └── jake@0.3.17 (minimatch@0.2.7) Then: $ geddy app todo_app /usr/lib/node_modules/geddy/bin/cli.js:177 throw err; ^ Error: Command failed: /bin/sh: jake: command not found at ChildProcess.exithandler (child_process.js:540:15) at ChildProcess.EventEmitter.emit (events.js:96:17) at maybeClose (child_process.js:638:16) at Socket.ChildProcess.spawn.stdin (child_process.js:815:11) at Socket.EventEmitter.emit (events.js:93:17) at Socket._destroy.destroyed (net.js:357:10) at process.startup.processNextTick.process._tickCallback (node.js:244:9) I googled and found that there was a similar https://github.com/geddy/geddy/issues/212 issue during 0.2: #67 The solution was to do a sudo npm install -g jake Thing is, should this issue be repeating? True, all it takes is some googling and deduction. However when following the tutorial at http://geddyjs.org/tutorial.html and hitting a show-stopper like this leaves a bad impression. The npm auto install of jake should probably be removed and the tutorial edited to include: """ geddy requires the jake module. Install jake globally: sudo npm install -g jake """ Right after the "npm install geddy" part. Cheers! mde commented Oct 5, 2012 You're right, this has historically been a big problem -- there's no way to specify that a dep in package.json has to be installed globally. Even the "prefer global" flag in Jake's package.json doesn't help this. The newest version of Geddy (0.5), which will likely be out in the next couple of days doesn't have this problem, as it uses the local Jake pulled down by NPM. You can try this out by grabbing the latest master. We'd love to have more people banging on it bef
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://stackoverflow.com/questions/6103121/express-command-not-found-in-bash-after-installing-it-with-npm workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join command not them; it only takes a minute: Sign up express command not found in bash after installing it with npm up vote 22 down vote favorite 13 just installed new ubuntu vm to test around with node installed things in this order: node mongodb-server npm express mongoose now, trying to create a new app i noticed express cannot be used command not found in the shell. express -v returns express: command not found i installed npm like this curl http://npmjs.org/install.sh | sudo sh and i installed express this way npm install express any ideas? bash node.js express npm share|improve this question asked May 23 '11 at 21:14 Sander 8,887135491 2 npm install -g express-generator , and cd myapp && npm install, expressjs.com/guide.html –miukki Apr 28 '14 at 3:21 add a comment| 7 Answers 7 active oldest votes up vote 38 down vote accepted npm install express -g You need to install it globally. Npm 1.0 installs modules locally by default. So the bash executable lives in /node_modules/bin/. You can add that folder to PATH or you can just install express globally so that it's picked up by PATH share|improve this answer answered May 23 '11 at 21:32 Raynos 110k33274341 2 You can also run scripts through npm by adding a "scripts" object to your package.json, and doing, "$ npm run-script scriptname". NPM adds the various bin directories in the local package repo to the path before runni