Skip to content


Error installing Devtools autosave #3242

roymendezc opened this Issue · 6 comments

4 participants


In Terminal:

roymacmini:~ jmrodea$ sudo npm install -g autosave
npm http GET
npm http 304
npm http GET
npm http 304
/usr/local/bin/autosave -> /usr/local/lib/node_modules/autosave/bin/autosave

autosave@1.0.3 install /usr/local/lib/node_modules/autosave
node ./scripts/install.js

sh: node: command not found
npm ERR! autosave@1.0.3 install: node ./scripts/install.js
npm ERR! sh "-c" "node ./scripts/install.js" failed with 127
npm ERR!
npm ERR! Failed at the autosave@1.0.3 install script.
npm ERR! This is most likely a problem with the autosave package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./scripts/install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls autosave
npm ERR! There is likely additional logging output above.

npm ERR! System Darwin 12.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "autosave"
npm ERR! cwd /Users/jmrodea
npm ERR! node -v v0.10.0
npm ERR! npm -v 1.2.14
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/jmrodea/npm-debug.log
npm ERR! not ok code 0


Are you using a weird shell that uses a special profile of something?

npm member

It looks to me like Node is not on your path under sudo. What happens when you run sudo node -v at the command line?


thanks for response,

when I put sudo node -v it shows this:

roymacmini:local jmrodea$

npm member

Yeah, so what you should have seen was your Node version printed out (i.e. "v0.10.0"). The fact that you're not seeing that does indicate that your path under sudo needs fixing. Not sure how to do that, though.


This is an issue with OS packages of node. They install node as nodejs.

To fix this you can use symbolic linking.

sudo ln -s /install_dir/nodejs /install_dir/node

in windows you can use the mklink command.. Be sure to open the command prompt as a administrator

@luk- luk- closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.