skill-sample-nodejs-adventure-game
skill-sample-nodejs-adventure-game copied to clipboard
Error During NPM Start
I have reviewed all other posts, and none seem to help. I keep getting this result: `
[email protected] start /Users/make717/interactive-adventure-game-tool node node_modules/gulp/bin/gulp.js
/Users/make717/interactive-adventure-game-tool/node_modules/require-dir/index.js:97 if (!require.extensions.hasOwnProperty(ext)) { ^
TypeError: require.extensions.hasOwnProperty is not a function
at requireDir (/Users/make717/interactive-adventure-game-tool/node_modules/require-dir/index.js:97:37)
at Object.node node_modules/gulp/bin/gulp.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /Users/make717/.npm/_logs/2018-01-22T18_33_44_967Z-debug.log`
Any Ideas?
I updated Node to the latest version (9.something) and am now getting this error: `
[email protected] start /Users/make717/interactive-adventure-game-tool node node_modules/gulp/bin/gulp.js
[13:38:24] Using gulpfile ~/interactive-adventure-game-tool/gulpfile.js
[13:38:24] Starting 'default'...
[13:38:24] Starting 'styles'...
[13:38:24] 'styles' errored after 104 ms
[13:38:24] Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (59)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v3.13.1
at module.exports (/Users/make717/interactive-adventure-game-tool/node_modules/node-sass/lib/binding.js:13:13)
at Object.node node_modules/gulp/bin/gulp.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /Users/make717/.npm/_logs/2018-01-22T18_38_24_204Z-debug.log`
Had the same issue, resolved for me by update package.json From "require-dir": "^0.2.0" to "require-dir": "0.3.2".