alexa-samples / skill-sample-nodejs-adventure-game

This tool provides an easy to use front-end that allows developers to instantly deploy code for your story, or use the generated code as a starting point for more complex projects.
Apache License 2.0
510 stars 218 forks source link

Gulp error #19

Open aubie11 opened 7 years ago

aubie11 commented 7 years ago

when try and run npm start - I get this. Not sure how to proceed. node in 7.3.0. npm 3.10.10

npm ERR! Darwin 16.0.0 npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" npm ERR! node v7.3.0 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! interactive-adventure-game-tool@1.0.0 start:node node_modules/gulp/bin/gulp.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the interactive-adventure-game-tool@1.0.0 start script 'node node_modules/gulp/bin/gulp.js'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the interactive-adventure-game-tool package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node node_modules/gulp/bin/gulp.js npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs interactive-adventure-game-tool npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls interactive-adventure-game-tool npm ERR! There is likely additional logging output above.

dragven commented 7 years ago

I'm not sure if you had already fixed this, but I had the same issue.

I'm not sure exactly which of these steps actually fixed it, but here's all the steps I took, and it started working:

(perform all of this from the local git repo directory)

brew update
brew uninstall node
brew install node
npm install
npm rebuild node-sass
npm start

I hope that helps. My assumption is I was on node-0.12, and some very old version of brew (as I don't typically use homebrew to install on my Mac). The npm rebuild node-sass is more likely required due to the change in your npm environment (the uninstall re-install)

Atmajr commented 7 years ago

I was having the same problem. Here's how I fixed it.

I can't be certain that all of these steps were required, but after pulling my hair out for hours, this is what finally got it working for me.