nodemon not working properly

Question

I am running my nodejs app by npm start

I just installed nodemon by sudo npm install -g nodemon so that i can get my server restarted when i save changes to files.

But when i try to start the server, something like this

nodemon ./app.js localhost 3000 or nodemon start localhost 3000

I get this as output

LM-SJC-00871929:webapp gdeep$ nodemon ./app.js localhost 3000
28 May 23:34:30 - [nodemon] v1.1.1
28 May 23:34:30 - [nodemon] to restart at any time, enter `rs`
28 May 23:34:30 - [nodemon] watching: *.*
28 May 23:34:30 - [nodemon] starting `node ./app.js localhost 3000`

but when i go to my webpage, i get

Oops! Google Chrome could not connect to localhost:3000. What am i doing wrong?

App.js here http://collabedit.com/t35dy

Your issue is likely not with nodemon. Post the contents of `app.js` — SomeKittens, May 29 '14 at 06:56
I just added app.js as part of the question. Thanks for helping out. — bruceparker, May 29 '14 at 06:58

SomeKittens · Accepted Answer · 2014-05-29T21:38:16.517

55

You're running express 4, which has the app.listen call in a different file than app.js. The command you're looking for is nodemon bin/www (localhost and 3000 are not needed in this scenario).

In fact, you can even run nodemon with no args, and it'll read what command needs to be run from scripts.start in package.json (which express generates automatically).

edited May 29 '14 at 21:38

answered May 29 '14 at 06:59

SomeKittens

38,868
19
114
143

3

If you try to run the express app with just node and not nodemon, you'll get the same error. Since express 4, the script that runs the server is actually in bin/www (note there's no .js extension). This www file reads your app.js *config* and runs the server. – Remy Sharp May 29 '14 at 21:12
2

Also worth adding that you can run express 4 based apps just using `nodemon` with no args, because it'll red from the package.json file and run the `scripts.start` option. – Remy Sharp May 29 '14 at 21:14

Skoua · Answer 2 · 2020-01-03T01:19:53.507

23

Here's what I did to make nodemon update correctly:

nodemon index.js -L

The -L flag stands for legacyWatch, here's an explanation from the official doc:

In some networked environments (such as a container running nodemon reading across a mounted drive), you will need to use the legacyWatch: true which enables Chokidar's polling.

https://www.npmjs.com/package/nodemon#application-isnt-restarting

edited Jan 03 '20 at 01:19

answered Mar 22 '19 at 15:06

Skoua

3,373
3
38
51

score 10 · Answer 3 · answered Jul 23 '17 at 15:14

10

In my case, I had to install nodemon globally. Use this command to do so..

npm install -g nodemon

If you're using Linux you may need to prefix the command with the sudo keyword for administration access..

sudo npm install -g nodemon

answered Jul 23 '17 at 15:14

Garth

3,237
2
18
28

score 8 · Answer 4 · answered May 29 '14 at 06:47

8

try running nodemon ./app.js 3000 or nodemon start 3000

answered May 29 '14 at 06:47

user3607134

108
1
7

This doesn't fix his problem. – SomeKittens May 29 '14 at 06:50
yes it doesn't. @SomeKittensUx2666, are you facing same problem too? – bruceparker May 29 '14 at 06:54

score 5 · Answer 5 · answered Feb 18 '15 at 11:51

5

For Express.js 4,
use nodemon
or
nodemon bin/www

answered Feb 18 '15 at 11:51

Dinesh

499
5
6

score 5 · Answer 6 · edited Jan 30 '16 at 17:31

5

Add following code in your code

app.js

app.listen(3000, function(){
    console.log("info",'Server is running at port : ' + 3000);
});

package.json
```
nodemon app.js 
```

Then run npm start from the command line.

edited Jan 30 '16 at 17:31

Tunaki

132,869
46
340
423

answered Jan 30 '16 at 17:30

BHUVNESH KUMAR

391
4
15

score 5 · Answer 7 · edited Mar 29 '21 at 07:41

5

npm i nodemon
Edit your Package.json file:- set start to nodemon:

"scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "nodemon server.js"
}

Run npm start to try the server

edited Mar 29 '21 at 07:41

mousetail

7,009
4
25
45

answered Mar 28 '21 at 14:46

ujjwal jain

61
1
3

score 2 · Answer 8 · answered Jul 24 '18 at 02:56

2

If you are using express4, the easiest way is to navigate to package.json and change "scripts": { "start": "node ./bin/www" }

to "scripts": { "start": "nodemon ./bin/www" }

answered Jul 24 '18 at 02:56

Yue Yin

166
4

score 0 · Answer 9 · answered Feb 06 '15 at 03:47

0

For Express 4; Just run

nodemon

command (with out any args) on the directory; this works for me.

answered Feb 06 '15 at 03:47

Jackal

2,591
3
25
29

score 0 · Answer 10 · answered Aug 07 '16 at 18:59

0

thanks you need to type this after to enter in the folder application with

cd your_project_folder

sudo nodemon bin/www

answered Aug 07 '16 at 18:59

eskander barhi

11
5

score 0 · Answer 11 · answered Aug 17 '20 at 19:59

0

Certain child processes related to your parent process may not be closed. Try to kill all the child processes.

Ref: https://github.com/remy/pstree

answered Aug 17 '20 at 19:59

Rituraj Kulshresth

1
1

score 0 · Answer 12 · answered Dec 06 '20 at 08:12

0

Use single quotation for multi-value args like `--exec'.

e.g. I changed "nodemon --exec yarn build-langs" to "nodemon --exec 'yarn build-langs'" and worked.

answered Dec 06 '20 at 08:12

Masih Jahangiri

9,489
3
45
51

score 0 · Answer 13 · answered Mar 02 '22 at 20:13

0

 "scripts": {
    "start": "nodemon app.js"
  },

check it, if it's true or not

answered Mar 02 '22 at 20:13

hilmidemirtas

40
1
6

score 0 · Answer 14 · edited Jan 24 '23 at 16:27

0

Try this:

First install nodemon by npm install nodemon or any command from the official website (https://www.npmjs.com/package/nodemon) Then start your nodemon by npx nodemon filename.js or if you have your package.json with you and the entry point is the file you would like to open then you can also go with the command npx nodemon Check this once

Hope it works!!

Happy Coding

edited Jan 24 '23 at 16:27

Tyler2P

2,324
26
22
31

answered Jan 23 '23 at 15:25

Challa Sai Mahitha Reddy

1

score 0 · Answer 15 · edited Jan 27 '23 at 16:15

0

You can directly use the command nodemon start to start your server.

edited Jan 27 '23 at 16:15

Tyler2P

2,324
26
22
31

answered Jan 26 '23 at 14:11

ankit das

1

score 0 · Answer 16 · edited Feb 22 '23 at 09:56

0

Try this command on terminal if you are using Nodejs & TypeScript

npm i --dev nodemon ts-node

edited Feb 22 '23 at 09:56

Khaled Ayed

1,121
3
12
29

answered Feb 14 '23 at 05:48

AMAY SANDANSHIV

1

score 0 · Answer 17 · answered May 25 '23 at 14:06

If the solutions don't work for you and you have Node.js 18 or higher installed, you no longer need to use nodemon. Instead, you can pass the --watch flag and Node will automatically restart the server for you:

node --watch index.js

Note: the --watch feature is experimental.

score -1 · Answer 18 · answered Sep 21 '15 at 21:02

-1

You might also run into the issue of having an empty .nodemonignore.

answered Sep 21 '15 at 21:02

czerasz

13,682
9
53
63

score -1 · Answer 19 · edited Nov 02 '19 at 17:58

-1

try

npm install --save-dev nodemon

and then in package.json file keep like this

"scripts": {
    "start": "nodemon",
    "test": "echo \"Error: no test specified\" && exit 1"
  },

instead of npx nodemon, which takes more time

edited Nov 02 '19 at 17:58

David Buck

3,752
35
31
35

answered Nov 02 '19 at 16:49

Sheshadri H

1
1

There are other answers and a accepted one that provide the OP's question, and they were posted some time ago. When posting an answer [see: How do I write a good answer?](https://stackoverflow.com/help/how-to-answer), please make sure you add either a new solution, or a substantially better explanation, especially when answering older questions. – help-info.de Nov 02 '19 at 18:01

score -1 · Answer 20 · edited Nov 03 '22 at 08:58

-1

First of all, uninstall nodemon:

npm uninstall nodemon

After uninstalling the nodemon then install nodemon globally using:

npm i -g nodemon

It will install nodemon globally then run the following command:

nodemon index.js or app.js

edited Nov 03 '22 at 08:58

nima

7,796
12
36
53

answered Oct 31 '22 at 07:35

Wasif Khan

1

nodemon not working properly

20 Answers20

Linked

Related