Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm start not working on windows10 #77

Open
miles182 opened this issue Jan 20, 2017 · 0 comments
Open

npm start not working on windows10 #77

miles182 opened this issue Jan 20, 2017 · 0 comments

Comments

@miles182
Copy link

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):

"scripts": {
    "start": "node ./node_modules/gulp/bin/gulp.js --production",
    "start-dev": "node  ./node_modules/gulp/bin/gulp.js",
    "build": "node ./node_modules/gulp/bin/gulp.js build --production",
    "test": "node ./node_modules/karma/bin/karma start karma.conf.js"
  }

I just wanted to log it here in case somebody else has the same problem and is looking for a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant