You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After cloning the repository and folliwing all configuration steps (npm/bower install etc.) the application fails to start via npm start., with the following error :
C:\Users\michael\IdeaProjects\a1-fusion>npm start
> [email protected] start C:\Users\michael\IdeaProjects\a1-fusion
> ./node_modules/gulp/bin/gulp.js --production
Der Befehl "." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `./node_modules/gulp/bin/gulp.js --production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script './node_modules/gulp/bin/gulp.js --production'.
npm ERR! This is most likely a problem with the lucidworks-view package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ./node_modules/gulp/bin/gulp.js --production
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs lucidworks-view
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls lucidworks-view
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\michael\IdeaProjects\a1-fusion\npm-debug.log
It seems to be a windows 10 and node issue, modyfing the scripts object in package.json allows to run npm start (add node to the path):
After cloning the repository and folliwing all configuration steps (npm/bower install etc.) the application fails to start via npm start., with the following error :
It seems to be a windows 10 and node issue, modyfing the scripts object in package.json allows to run npm start (add node to the path):
I just wanted to log it here in case somebody else has the same problem and is looking for a solution.
The text was updated successfully, but these errors were encountered: