Earlier today I installed gulp-cli for another project workflow, and guess what! It caused conflicts with gulp in my local Simpleweather workflow. Gulp ended up being moved into another path:
ERR! File exists: /usr/local/bin/gulp
When I tried to start gulp in Simpleweather, this is what appeared in Terminal:
argv "/usr/local/bin/node" "/usr/local/bin/<a class="zem_slink" title="Npm (software)" href="http://npmjs.org/" target="_blank" rel="homepage">npm</a>" "install" "-g" "gulp"
npm ERR! node v6.3.0
npm ERR! npm v3.10.3
npm ERR! path /usr/local/bin/gulp
npm ERR! code EEXIST
npm ERR! Refusing to delete /usr/local/bin/gulp: ../lib/node_modules/gulp-cli/bin/gulp.js symlink target is not controlled by npm /usr/local
npm ERR! File exists: /usr/local/bin/gulp
npm ERR! Move it away, and try again.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/mariacam/Development/simpleweather/workflows/npm-debug.log
So how was I going to fix this?
<span class="pln">cd </span><span class="pun">/</span><span class="pln">usr</span><span class="pun">/</span><span class="kwd">local</span><span class="pun">/</span><span class="pln">bin
ls </span><span class="pun">-</span><span class="pln">las</span>
if gulp is present delete that directory. (sudo rm -r gulp) reinstall gulp-cli (I removed the “f” from sudo rm -rf gulp)
if it is not working uninstall node, npm completely and try again
follow this link for step by step guide
I have found that if you remove things and then re-install, it should work. So I went into /usr/local/bin and removed the gulp folder. Then I kept on hitting cd until I got to my root folder ‘/:’. But that’s not where I wanted to be! I wanted to get back to my home directory where my subdirectory development resides. Someone reminded me that I could either type cd and hit return or ~ and hit return, and that would take me back to my home directory. And it did!
So now I had to re-install gulp globally and then re-install all my dev dependencies so that my workflow would work again. Let’s hope that it does, because I updated to the latest version of nodejs and npm after I had already created this workflow. I will update this with another post and will link to this one as well. Stay tuned!