Trouble starting with npm #147

jcs224 · 2014-12-01T21:28:50Z

Trouble starting Node server with 'npm start', I get the following error. Same thing for both a local as well as Vagrant install. Here is my npm-debug.log file:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@1.4.9
3 info using node@v0.10.28
4 verbose node symlink /usr/bin/node
5 verbose run-script [ 'prestart', 'start', 'poststart' ]
6 info prestart foundation-apps-template@0.0.1
7 info start foundation-apps-template@0.0.1
8 verbose unsafe-perm in lifecycle true
9 info foundation-apps-template@0.0.1 Failed to exec start script
10 error foundation-apps-template@0.0.1 start: `gulp`
10 error Exit status 8
11 error Failed at the foundation-apps-template@0.0.1 start script.
11 error This is most likely a problem with the foundation-apps-template package,
11 error not with npm itself.
11 error Tell the author that this fails on your system:
11 error     gulp
11 error You can get their info via:
11 error     npm owner ls foundation-apps-template
11 error There is likely additional logging output above.
12 error System Linux 3.13.0-11-generic
13 error command "/usr/bin/node" "/usr/bin/npm" "start"
14 error cwd /home/vagrant/Websites/foundation_app
15 error node -v v0.10.28
16 error npm -v 1.4.9
17 error code ELIFECYCLE
18 verbose exit [ 1, true ]

Looks like Gulp is the culprit, but I know it's installed on my system.

What am I doing wrong? Is anyone else having this issue?

Thanks!

The text was updated successfully, but these errors were encountered:

alexprice1 · 2014-12-02T05:29:50Z

'npm start' runs a script that runs Gulp.

To see the actual error, just run 'gulp'.

AntJanus · 2014-12-02T14:54:39Z

@jcs224 Please run Gulp and post the output, and run npm install before that if you haven't already.

jcs224 · 2014-12-02T15:41:52Z

Error: Cannot find module './bower_components/foundation-apps/bin/gulp-dynamic-routing'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/sweeney/Dropbox/Websites/foundation_app/gulpfile.js:12:22)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

alexprice1 · 2014-12-02T15:42:39Z

Run bower install

jcs224 · 2014-12-02T15:51:11Z

Looks like it's working now. Thank you!

alexprice1 · 2014-12-20T19:18:29Z

You get this error when the port is being used by another process. You may already be running the Gulp process? Or a Node sever on the same port?

Sent on a Sprint Samsung Galaxy S® 5

-------- Original message --------
From: Tuly- notifications@github.com
Date:12/20/2014 11:51 AM (GMT-06:00)
To: zurb/foundation-apps foundation-apps@noreply.github.com
Cc: Alexander Price price.alex@yahoo.com
Subject: Re: [foundation-apps] Trouble starting with npm (#147)

I've a problem doing the same thing, but it's a bit different. If I run "gulp" in my app dir, it returns this

root@ubuntu:~/myApp# gulp
[18:49:58] Using gulpfile ~/myApp/gulpfile.js
[18:49:58] Starting 'build'...
[18:49:58] Starting 'clean'...
[18:49:58] Starting 'server:start'...
[18:49:58] Finished 'server:start' after 6.29 ms
[18:49:58] Finished 'build' after 7.9 ms
[18:49:58] Starting 'default'...
[18:49:58] Finished 'default' after 7.87 ms

events.js:72
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1039:14)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at ConnectApp.server (/home/tuly/myApp/node_modules/gulp-connect/index.js:57:19)
at new ConnectApp (/home/tuly/myApp/node_modules/gulp-connect/index.js:37:10)
at Object.module.exports.server (/home/tuly/myApp/node_modules/gulp-connect/index.js:170:12)
at Gulp. (/home/tuly/myApp/gulpfile.js:134:11)
at module.exports (/home/tuly/myApp/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
at Gulp.Orchestrator._runTask (/home/tuly/myApp/node_modules/gulp/node_modules/orchestrator/index.js:273:3)

What can I do ?
Thanks

—
Reply to this email directly or view it on GitHub.

andreatulimiero · 2014-12-21T10:31:29Z

Hi,
Thanks for the attention, I don't know why but it's now working !

2014-12-20 20:18 GMT+01:00 Alexander Price notifications@github.com:

You get this error when the port is being used by another process. You may
already be running the Gulp process? Or a Node sever on the same port?

Sent on a Sprint Samsung Galaxy S® 5

-------- Original message --------
From: Tuly- notifications@github.com
Date:12/20/2014 11:51 AM (GMT-06:00)
To: zurb/foundation-apps foundation-apps@noreply.github.com
Cc: Alexander Price price.alex@yahoo.com
Subject: Re: [foundation-apps] Trouble starting with npm (#147)

I've a problem doing the same thing, but it's a bit different. If I run
"gulp" in my app dir, it returns this

root@ubuntu:~/myApp# gulp
[18:49:58] Using gulpfile ~/myApp/gulpfile.js
[18:49:58] Starting 'build'...
[18:49:58] Starting 'clean'...
[18:49:58] Starting 'server:start'...
[18:49:58] Finished 'server:start' after 6.29 ms
[18:49:58] Finished 'build' after 7.9 ms
[18:49:58] Starting 'default'...
[18:49:58] Finished 'default' after 7.87 ms

events.js:72
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1039:14)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at ConnectApp.server
(/home/tuly/myApp/node_modules/gulp-connect/index.js:57:19)
at new ConnectApp
(/home/tuly/myApp/node_modules/gulp-connect/index.js:37:10)
at Object.module.exports.server
(/home/tuly/myApp/node_modules/gulp-connect/index.js:170:12)
at Gulp. (/home/tuly/myApp/gulpfile.js:134:11)
at module.exports
(/home/tuly/myApp/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
at Gulp.Orchestrator._runTask
(/home/tuly/myApp/node_modules/gulp/node_modules/orchestrator/index.js:273:3)

What can I do ?
Thanks

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#147 (comment)
.

Andrea Tulimiero

alexprice1 · 2014-12-21T16:05:36Z

Are you trying to run it locally?

-------- Original message --------
From: Tuly- notifications@github.com
Date:12/21/2014 4:31 AM (GMT-06:00)
To: zurb/foundation-apps foundation-apps@noreply.github.com
Cc: Alexander Price price.alex@yahoo.com
Subject: Re: [foundation-apps] Trouble starting with npm (#147)

Hi,
Thanks for the attention, I don't know why but it's now working !

2014-12-20 20:18 GMT+01:00 Alexander Price notifications@github.com:

You get this error when the port is being used by another process. You may
already be running the Gulp process? Or a Node sever on the same port?

Sent on a Sprint Samsung Galaxy S® 5

-------- Original message --------
From: Tuly- notifications@github.com
Date:12/20/2014 11:51 AM (GMT-06:00)
To: zurb/foundation-apps foundation-apps@noreply.github.com
Cc: Alexander Price price.alex@yahoo.com
Subject: Re: [foundation-apps] Trouble starting with npm (#147)

I've a problem doing the same thing, but it's a bit different. If I run
"gulp" in my app dir, it returns this

root@ubuntu:~/myApp# gulp
[18:49:58] Using gulpfile ~/myApp/gulpfile.js
[18:49:58] Starting 'build'...
[18:49:58] Starting 'clean'...
[18:49:58] Starting 'server:start'...
[18:49:58] Finished 'server:start' after 6.29 ms
[18:49:58] Finished 'build' after 7.9 ms
[18:49:58] Starting 'default'...
[18:49:58] Finished 'default' after 7.87 ms

events.js:72
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1039:14)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at ConnectApp.server
(/home/tuly/myApp/node_modules/gulp-connect/index.js:57:19)
at new ConnectApp
(/home/tuly/myApp/node_modules/gulp-connect/index.js:37:10)
at Object.module.exports.server
(/home/tuly/myApp/node_modules/gulp-connect/index.js:170:12)
at Gulp. (/home/tuly/myApp/gulpfile.js:134:11)
at module.exports
(/home/tuly/myApp/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
at Gulp.Orchestrator._runTask
(/home/tuly/myApp/node_modules/gulp/node_modules/orchestrator/index.js:273:3)

What can I do ?
Thanks

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#147 (comment)
.

Andrea Tulimiero
—
Reply to this email directly or view it on GitHub.

niwong · 2014-12-22T00:28:38Z

@chapinkapa I have a similar problem.
When I run gulp:

Error: Cannot find module 'core-util-is'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/Users/NickWong/Desktop/Projects/FoundationApp/node_modules/through2/node_modules/readable-stream/lib/_stream_duplex.js:39:12)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

alexprice1 · 2014-12-22T14:48:45Z

Make sure you are in the correct directory.

Run npm install.
Run bower install

Sent on a Sprint Samsung Galaxy S® 5

-------- Original message --------
From: Nick notifications@github.com
Date:12/21/2014 6:28 PM (GMT-06:00)
To: zurb/foundation-apps foundation-apps@noreply.github.com
Cc: Alexander Price price.alex@yahoo.com
Subject: Re: [foundation-apps] Trouble starting with npm (#147)

@chapinkapa I have a similar problem.
When I run gulp:

Error: Cannot find module 'core-util-is'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/Users/NickWong/Desktop/Projects/FoundationApp/node_modules/through2/node_modules/readable-stream/lib/_stream_duplex.js:39:12)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

—
Reply to this email directly or view it on GitHub.

niwong · 2014-12-23T10:29:45Z

I followed those directions, then ran 'npm start' in the directory.

npm ERR! foundation-apps-template@0.0.1 start: gulp
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the foundation-apps-template@0.0.1 start script.
npm ERR! This is most likely a problem with the foundation-apps-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp
npm ERR! You can get their info via:
npm ERR! npm owner ls foundation-apps-template
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 14.0.0
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! cwd /Users/NickWong/Desktop/Projects/FoundationApp
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/NickWong/Desktop/Projects/FoundationApp/npm-debug.log
npm ERR! not ok code 0

Tried "sudo'ing'" it.

Nicks-MacBook-Pro:FoundationApp NickWong$ sudo npm start

foundation-apps-template@0.0.1 start /Users/NickWong/Desktop/Projects/FoundationApp
gulp

module.js:340
throw err;
^
Error: Cannot find module 'core-util-is'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/Users/NickWong/Desktop/Projects/FoundationApp/node_modules/through2/node_modules/readable-stream/lib/_stream_duplex.js:39:12)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

npm ERR! foundation-apps-template@0.0.1 start: gulp
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the foundation-apps-template@0.0.1 start script.
npm ERR! This is most likely a problem with the foundation-apps-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp
npm ERR! You can get their info via:
npm ERR! npm owner ls foundation-apps-template
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 14.0.0
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! cwd /Users/NickWong/Desktop/Projects/FoundationApp
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/NickWong/Desktop/Projects/FoundationApp/npm-debug.log
npm ERR! not ok code 0

niwong · 2014-12-25T22:04:34Z

I figured it out, thank you for your help!!! Merry Christmas

alexprice1 · 2014-12-25T22:34:26Z

Awesome! Merry Christmas!

marbio · 2015-03-09T19:19:35Z

"npm install" works for me

jcs224 closed this as completed Dec 2, 2014

dredgerman mentioned this issue Nov 24, 2015

foundation-apps doesnt work and manual method produces hung process #721

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Trouble starting with npm #147

Trouble starting with npm #147

jcs224 commented Dec 1, 2014

alexprice1 commented Dec 2, 2014

AntJanus commented Dec 2, 2014

jcs224 commented Dec 2, 2014

alexprice1 commented Dec 2, 2014

jcs224 commented Dec 2, 2014

alexprice1 commented Dec 20, 2014

andreatulimiero commented Dec 21, 2014

alexprice1 commented Dec 21, 2014

niwong commented Dec 22, 2014

alexprice1 commented Dec 22, 2014

niwong commented Dec 23, 2014

niwong commented Dec 25, 2014

alexprice1 commented Dec 25, 2014

marbio commented Mar 9, 2015

Trouble starting with npm #147

Trouble starting with npm #147

Comments

jcs224 commented Dec 1, 2014

alexprice1 commented Dec 2, 2014

AntJanus commented Dec 2, 2014

jcs224 commented Dec 2, 2014

alexprice1 commented Dec 2, 2014

jcs224 commented Dec 2, 2014

alexprice1 commented Dec 20, 2014

andreatulimiero commented Dec 21, 2014

alexprice1 commented Dec 21, 2014

niwong commented Dec 22, 2014

alexprice1 commented Dec 22, 2014

niwong commented Dec 23, 2014

niwong commented Dec 25, 2014

alexprice1 commented Dec 25, 2014

marbio commented Mar 9, 2015