Running NodeJS command after another

Question

I'm using NodeJS to do two things:

Start a server and listen on a port
Run a grunt task

The calls are as follows:

node livereload.js
grunt watch

But the problem is that the first call doesn't allow subsequent tasks to be run! So I have to do CTRL+C in the cmd to run another command.

Even doing:

node livereload.js & grunt watch

Doesn't work! Do I have to do something in the livereload.js file to make it exit the command so I can call another one?

The file looks like:

var lrserver = require('tiny-lr')();
lrserver.listen(35729, function(err) { console.log('LR Server Started'); });

I've even tried:

node livereload
.exit
grunt watch

But that doesn't work either.

Update: It seems that the grunt watch command is in fact being run with my first code example, but because it doesn't get exited it doesn't show the console logs from grunt because it's still on the livereload one. Any ideas what the best way to fix this is then?

What's the correct way to do CTRL+C but from NodeJS? It would seem I need to do this after the console.log

You give node a script to listen to a port indefinitely, and question why it doesn't stop listening without Ctrl+C? Well, why should it stop listening if you tell it to listen? Downvoted for question having no logical base. Also next time include the code you run, accidentally found it here: github.com/mklabs/tiny-lr/issues/73 — alandarev
– alandarev, Commented Mar 9, 2015 at 17:20
No. I feel sorry for the answer authors as they tried to answer meaningless question. — alandarev
– alandarev, Commented Mar 9, 2015 at 17:22
@alandarev Then go outside then if this question is meaningless to you. Because it's relevant to me! — Cameron
– Cameron, Commented Mar 9, 2015 at 17:23

Tom Hallam · Accepted Answer · 2015-03-09 16:44:22Z

2

I think this is what you are after:

node livereload.js && grunt watch

answered Mar 9, 2015 at 16:44

Tom Hallam

1,94816 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Cameron Over a year ago

The command runs as I've discovered. But I don't see the console logs from the grunt watch command as cmd is still on the previous command.

Tom Hallam Over a year ago

Ok sorry, I didn't realise you were operating in Windows - see Lee Daniel Crocker's answer above.

Lee Daniel Crocker · Accepted Answer · 2015-03-09 16:51:11Z

1

In Windows, try:

start /B node livereload.js

That's roughly the equivalent of Linux's

node livereload.js &

answered Mar 9, 2015 at 16:51

Lee Daniel Crocker

13.3k4 gold badges33 silver badges56 bronze badges

5 Comments

Cameron Over a year ago

Still get the flashing _ after the command unless I do CTRL+C

Lee Daniel Crocker Over a year ago

I don't know what your code is doing. Maybe it specifically listens for keyboard input, so it's not designed to be backgrounded?

Lee Daniel Crocker Over a year ago

I would assume process.exit(), but I'm sure that's not what you want.

Cameron Over a year ago

Ah yeah that just closes the cmd prompt so it's not the same. I'm asking the guys who created the livereload module to find out why it's not exiting without CTRL+C here: github.com/mklabs/tiny-lr/issues/73

Cameron Over a year ago

So it seems like START /B is the best way to handle this according to the guys who developed the module. Thanks for the help.

Collectives™ on Stack Overflow

Running NodeJS command after another

2 Answers 2

2 Comments

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related