Skj
Skj

Reputation: 101

Why can't execute "npm start" or even other npm commands?

What could the problem be? I get this error whenever i run "npm start" or even basic commands like "npm install." I am trying to figure out why it can't run.

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 [email protected]
3 info using [email protected]
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 verbose run-script [ 'prestart', 'start', 'poststart' ]
6 info prestart [email protected]
7 info start [email protected]
8 verbose unsafe-perm in lifecycle true
9 info [email protected] Failed to exec start script
10 error [email protected] start: `node ./bin/www`
10 error spawn ENOENT
11 error Failed at the [email protected] start script.
11 error This is most likely a problem with the nodetest1 package,
11 error not with npm itself.
11 error Tell the author that this fails on your system:
11 error     node ./bin/www
11 error You can get their info via:
11 error     npm owner ls nodetest1
11 error There is likely additional logging output above.
12 error System Windows_NT 6.1.7601
13 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
14 error cwd C:\Users\Kijo\nodetest1
15 error node -v v0.10.32
16 error npm -v 1.4.28
17 error syscall spawn
18 error code ELIFECYCLE
19 error errno ENOENT
20 verbose exit [ 1, true ]

@nox3011 Here is a printout of my directory, if it can help.Project Directory.

Upvotes: 1

Views: 3884

Answers (1)

nox0311
nox0311

Reputation: 76

You have a ENOENT error which means it was not able to locate some required file or directory. Mostly with ./bin/www Try running npm start by changing directory to C:\Program Files\node

Upvotes: 1

Related Questions