After running nmp run serve from Command Promt Prompt does not become available
After running npm run serve I receive a message saying
Server listening at localhost:8888
But
now I don't get the prompt back it just got stuck there
Thanks for your help
node.js
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
add a comment |
After running npm run serve I receive a message saying
Server listening at localhost:8888
But
now I don't get the prompt back it just got stuck there
Thanks for your help
node.js
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
add a comment |
After running npm run serve I receive a message saying
Server listening at localhost:8888
But
now I don't get the prompt back it just got stuck there
Thanks for your help
node.js
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
After running npm run serve I receive a message saying
Server listening at localhost:8888
But
now I don't get the prompt back it just got stuck there
Thanks for your help
node.js
node.js
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
asked Nov 19 '18 at 2:10
Javier_CaceresJavier_Caceres
206
206
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That is normal, no command prompt as the server is still running until you hit CTRL-C to stop it. However, it is possible to do what you want by adding an ampersand "&" at the end of your command. Example:
npm run &
It should show you the PID number after it runs, so to kill it type:
kill <whatever the PID number is>
Didn't see the PID number?? type this to list running processes:
ps -aef
Alternate way is to use "screen" or "tmux", which allows you to multiplex the terminal.
answered Nov 19 '18 at 2:16
Mark BMark B
6619
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53367414%2fafter-running-nmp-run-serve-from-command-promt-prompt-does-not-become-available%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That is normal, no command prompt as the server is still running until you hit CTRL-C to stop it. However, it is possible to do what you want by adding an ampersand "&" at the end of your command. Example:
npm run &
It should show you the PID number after it runs, so to kill it type:
kill <whatever the PID number is>
Didn't see the PID number?? type this to list running processes:
ps -aef
Alternate way is to use "screen" or "tmux", which allows you to multiplex the terminal.
answered Nov 19 '18 at 2:16
Mark BMark B
6619
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
add a comment |
That is normal, no command prompt as the server is still running until you hit CTRL-C to stop it. However, it is possible to do what you want by adding an ampersand "&" at the end of your command. Example:
npm run &
It should show you the PID number after it runs, so to kill it type:
kill <whatever the PID number is>
Didn't see the PID number?? type this to list running processes:
ps -aef
Alternate way is to use "screen" or "tmux", which allows you to multiplex the terminal.
answered Nov 19 '18 at 2:16
Mark BMark B
6619
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
add a comment |
That is normal, no command prompt as the server is still running until you hit CTRL-C to stop it. However, it is possible to do what you want by adding an ampersand "&" at the end of your command. Example:
npm run &
It should show you the PID number after it runs, so to kill it type:
kill <whatever the PID number is>
Didn't see the PID number?? type this to list running processes:
ps -aef
Alternate way is to use "screen" or "tmux", which allows you to multiplex the terminal.
answered Nov 19 '18 at 2:16
Mark BMark B
6619
That is normal, no command prompt as the server is still running until you hit CTRL-C to stop it. However, it is possible to do what you want by adding an ampersand "&" at the end of your command. Example:
npm run &
It should show you the PID number after it runs, so to kill it type:
kill <whatever the PID number is>
Didn't see the PID number?? type this to list running processes:
ps -aef
Alternate way is to use "screen" or "tmux", which allows you to multiplex the terminal.
answered Nov 19 '18 at 2:16
Mark BMark B
6619
edited Nov 19 '18 at 2:45
answered Nov 19 '18 at 2:16
Mark BMark B
6619
answered Nov 19 '18 at 2:16
Mark BMark B
6619
answered Nov 19 '18 at 2:16
Mark BMark B
6619
6619
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
add a comment |
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
Thanks but I did Contrl+C to close it for a fresh start and then wrote " nmp run serve &" and got to see the PID number just before the message where the Server listening at localhost:8888 comes up, the thing is I can't kill anything because I can;t write anything, the prompt is just not there
– Javier_Caceres
Nov 19 '18 at 2:30
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
as long as you didn't get any errors when you ran it, you just wait a few seconds and the command prompt should return. If not, you can use Screen: rackaid.com/blog/linux-screen-tutorial-and-how-to or tmux: hamvocke.com/blog/a-quick-and-easy-guide-to-tmux
– Mark B
Nov 19 '18 at 2:39
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Thank you Mark, TMux looks very good, too bad I can't use it her because I am running under windows.
– Javier_Caceres
Nov 19 '18 at 13:08
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Man, so sorry. I'm out of ideas other than opening a second terminal window. Best of luck, hope someone has better ideas!!
– Mark B
Nov 19 '18 at 15:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
Any luck yet? Curious on what worked for you...
– Mark B
Nov 21 '18 at 1:17
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53367414%2fafter-running-nmp-run-serve-from-command-promt-prompt-does-not-become-available%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
