I am .net developer.Previous developer used nodeJS and react for one project.I must complete that project.That project use nodeJS,and reactJS.I installed NodeJS in windows 8
I install packages(npm install) it worked well.But now I try to run-start project but it give error
When I write npm start it give that error
Failed at the react-seed #0.0.13 start script node_env=development node dev-server .webpack/config
here is log file
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#2.14.20
3 info using node#v4.4.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart react-seed#0.0.13
6 verbose unsafe-perm in lifecycle true
7 info start react-seed#0.0.13
8 verbose unsafe-perm in lifecycle true
9 info react-seed#0.0.13 Failed to exec start script
10 verbose stack Error: react-seed#0.0.13 start: `NODE_ENV=development node dev-server ./webpack/config`
10 verbose stack Exit status 1
10 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:214:16)
10 verbose stack at emitTwo (events.js:87:13)
10 verbose stack at EventEmitter.emit (events.js:172:7)
10 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
10 verbose stack at emitTwo (events.js:87:13)
10 verbose stack at ChildProcess.emit (events.js:172:7)
10 verbose stack at maybeClose (internal/child_process.js:827:16)
10 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
11 verbose pkgid react-seed#0.0.13
12 verbose cwd C:\nodeAQ
13 error Windows_NT 6.3.9600
14 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
15 error node v4.4.1
16 error npm v2.14.20
17 error code ELIFECYCLE
18 error react-seed#0.0.13 start: `NODE_ENV=development node dev-server ./webpack/config`
18 error Exit status 1
19 error Failed at the react-seed#0.0.13 start script 'NODE_ENV=development node dev-server ./webpack/config'.
19 error This is most likely a problem with the react-seed package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error NODE_ENV=development node dev-server ./webpack/config
19 error You can get information on how to open an issue for this project with:
19 error npm bugs react-seed
19 error Or if that isn't available, you can get their info via:
19 error
19 error npm owner ls react-seed
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]
Related
I have downloaded EJS master branch from https://github.com/mde/ejs and proceed to generate full public & private API docs throught the next indication:
This project uses JSDoc. For the full public API documentation, clone
the repository and run npm run doc. This will run JSDoc with the
proper options and output the documentation to out/. If you want the
both the public & private API docs, run npm run devdoc instead.
However i get a error related to jake, which is already installed.
npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'devdoc' ]
2 info using npm#2.15.9
3 info using node#v4.6.0
4 verbose run-script [ 'predevdoc', 'devdoc', 'postdevdoc' ]
5 info predevdoc ejs#2.5.2
6 info devdoc ejs#2.5.2
7 verbose unsafe-perm in lifecycle true
8 info ejs#2.5.2 Failed to exec devdoc script
9 verbose stack Error: ejs#2.5.2 devdoc: `jake doc[dev]`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:217:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at EventEmitter.emit (events.js:172:7)
9 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:829:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid ejs#2.5.2
11 verbose cwd C:\Users\ \Desktop\ejs-master
12 error Windows_NT 6.1.7601
13 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "devdoc"
14 error node v4.6.0
15 error npm v2.15.9
16 error code ELIFECYCLE
17 error ejs#2.5.2 devdoc: `jake doc[dev]`
17 error Exit status 1
18 error Failed at the ejs#2.5.2 devdoc script 'jake doc[dev]'.
18 error This is most likely a problem with the ejs package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error jake doc[dev]
18 error You can get information on how to open an issue for this project with:
18 error npm bugs ejs
18 error Or if that isn't available, you can get their info via:
18 error
18 error npm owner ls ejs
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]
I got the project from the Heroku startup guide and deployed it successfully. However when I try to run it locally I'm faced with this error:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#2.15.5
3 info using node#v4.4.5
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart MEAN#1.0.0
6 info start MEAN#1.0.0
7 verbose unsafe-perm in lifecycle true
8 info MEAN#1.0.0 Failed to exec start script
9 verbose stack Error: MEAN#1.0.0 start: `node server.js`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:217:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at EventEmitter.emit (events.js:172:7)
9 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:827:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid MEAN#1.0.0
11 verbose cwd C:\Users\kmagl\Documents\CuttingEdge\new-project4
12 error Windows_NT 10.0.10586
13 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
14 error node v4.4.5
15 error npm v2.15.5
16 error code ELIFECYCLE
17 error MEAN#1.0.0 start: `node server.js`
17 error Exit status 1
18 error Failed at the MEAN#1.0.0 start script 'node server.js'.
18 error This is most likely a problem with the MEAN package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error node server.js
18 error You can get information on how to open an issue for this project with:
18 error npm bugs MEAN
18 error Or if that isn't available, you can get their info via:
18 error
18 error npm owner ls MEAN
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]
I would love some help on this. I and some other people are having trouble at this point.
Make sure you've run npm install locally, and that you have an environment variable named MONGODB_URI that has a valid URL to a running mongodb instance.
Also, if you call node server.js from the command line, you may find more verbose logging to help you narrow down the problem; the one npm emits is usually pretty opaque.
I installed the replay starter kit on my windows 10 machine, but I get errors after "npm start." The key failure seems to be at 'babel-node ./server.js'.
Here's my npm debug log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files (x86)\\nodejs\\\\node.exe',
1 verbose cli 'C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#2.11.2
3 info using node#v0.12.5
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart relay-starter-kit#0.1.0
6 info start relay-starter-kit#0.1.0
7 verbose unsafe-perm in lifecycle true
8 info relay-starter-kit#0.1.0 Failed to exec start script
9 verbose stack Error: relay-starter-kit#0.1.0 start: `babel-node ./server.js`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\lifecycle.js:213:16)
9 verbose stack at EventEmitter.emit (events.js:110:17)
9 verbose stack at ChildProcess.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at ChildProcess.emit (events.js:110:17)
9 verbose stack at maybeClose (child_process.js:1015:16)
9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
10 verbose pkgid relay-starter-kit#0.1.0
11 verbose cwd C:\Users\Polisander\Code\miles-relay
12 error Windows_NT 6.3.9600
13 error argv "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
14 error node v0.12.5
15 error npm v2.11.2
16 error code ELIFECYCLE
17 error relay-starter-kit#0.1.0 start: `babel-node ./server.js`
17 error Exit status 1
18 error Failed at the relay-starter-kit#0.1.0 start script 'babel-node ./server.js'.
18 error This is most likely a problem with the relay-starter-kit package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error babel-node ./server.js
18 error You can get their info via:
18 error npm owner ls relay-starter-kit
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]
I'm just starting here so sorry in advance if this seems obvious,
I've been getting myself accustomed with the appengine back-end and am following Google's bookshelf example as a start.
Everything was going okay until I run the NPM run-script init-cloudsql command and for some reason after I enter the host IP of my db the cmd skips the user prompt and asks me for the password. Then it tried to launch the script with an anonymous user.
I'm following the instructions as described, I get no errors in the previous steps.
Below is the log of my run-script:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\barda\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run-script',
1 verbose cli 'init-cloudsql' ]
2 info using npm#3.5.0
3 info using node#v4.2.2
4 verbose run-script [ 'preinit-cloudsql', 'init-cloudsql', 'postinit-cloudsql' ]
5 info lifecycle nodejs-getting-started#1.0.0~preinit-cloudsql: nodejs-getting-started#1.0.0
6 silly lifecycle nodejs-getting-started#1.0.0~preinit-cloudsql: no script for preinit-cloudsql, continuing
7 info lifecycle nodejs-getting-started#1.0.0~init-cloudsql: nodejs-getting-started#1.0.0
8 verbose lifecycle nodejs-getting-started#1.0.0~init-cloudsql: unsafe-perm in lifecycle true
9 verbose lifecycle nodejs-getting-started#1.0.0~init-cloudsql: PATH: C:\Users\barda\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\nodejs-getting-started-2-structured-data\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Skype\Phone\;C:\apache-maven-3.3.9\bin\;C:\Users\barda\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin;C:\Users\barda\AppData\Roaming\npm;C:\Program Files\nodejs\
10 verbose lifecycle nodejs-getting-started#1.0.0~init-cloudsql: CWD: C:\nodejs-getting-started-2-structured-data
11 silly lifecycle nodejs-getting-started#1.0.0~init-cloudsql: Args: [ '/d /s /c', 'node books/model-cloudsql.js' ]
12 silly lifecycle nodejs-getting-started#1.0.0~init-cloudsql: Returned: code: 1 signal: null
13 info lifecycle nodejs-getting-started#1.0.0~init-cloudsql: Failed to exec init-cloudsql script
14 verbose stack Error: nodejs-getting-started#1.0.0 init-cloudsql: `node books/model-cloudsql.js`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (C:\Users\barda\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:87:13)
14 verbose stack at EventEmitter.emit (events.js:172:7)
14 verbose stack at ChildProcess.<anonymous> (C:\Users\barda\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack at emitTwo (events.js:87:13)
14 verbose stack at ChildProcess.emit (events.js:172:7)
14 verbose stack at maybeClose (internal/child_process.js:818:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid nodejs-getting-started#1.0.0
16 verbose cwd C:\nodejs-getting-started-2-structured-data
17 error Windows_NT 10.0.10586
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\barda\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run-script" "init-cloudsql"
19 error node v4.2.2
20 error npm v3.5.0
21 error code ELIFECYCLE
22 error nodejs-getting-started#1.0.0 init-cloudsql: `node books/model-cloudsql.js`
22 error Exit status 1
23 error Failed at the nodejs-getting-started#1.0.0 init-cloudsql script 'node books/model-cloudsql.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the nodejs-getting-started package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node books/model-cloudsql.js
23 error You can get their info via:
23 error npm owner ls nodejs-getting-started
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
I`m trying to run this app [surveyman][1] but without success,
the $npm run start command return this log :
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files (x86)\\nodejs\\\\node.exe',
1 verbose cli 'C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start' ]
2 info using npm#2.11.3
3 info using node#v0.12.7
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart react-surveyman#0.0.1
6 info start react-surveyman#0.0.1
7 verbose unsafe-perm in lifecycle true
8 info react-surveyman#0.0.1 Failed to exec start script
9 verbose stack Error: react-surveyman#0.0.1 start: `./node_modules/webpack-dev-server/bin/webpack-dev-server.js --progress --colors --port 8090`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\lifecycle.js:213:16)
9 verbose stack at EventEmitter.emit (events.js:110:17)
9 verbose stack at ChildProcess.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at ChildProcess.emit (events.js:110:17)
9 verbose stack at maybeClose (child_process.js:1015:16)
9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
10 verbose pkgid react-surveyman#0.0.1
11 verbose cwd C:\Users\Dev\react-surveyman
12 error Windows_NT 6.3.9600
13 error argv "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start"
14 error node v0.12.7
15 error npm v2.11.3
16 error code ELIFECYCLE
17 error react-surveyman#0.0.1 start: `./node_modules/webpack-dev-server/bin/webpack-dev-server.js --progress --colors --port 8090`
17 error Exit status 1
18 error Failed at the react-surveyman#0.0.1 start script './node_modules/webpack-dev-server/bin/webpack-dev-server.js --progress --colors --port 8090'.
18 error This is most likely a problem with the react-surveyman package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error ./node_modules/webpack-dev-server/bin/webpack-dev-server.js --progress --colors --port 8090
18 error You can get their info via:
18 error npm owner ls react-surveyman
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]
I'm using npm#2.11.3 with node#v0.12.7,
Any suggestion?
Thanks,
issue resolved, the issue is because I'm on windows and the node scripts are not windows friendly.by removing the "./" from "./node_modules/webpack-dev-server/bin/webpack-dev-server.js --progress --colors --port 8090",