Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Nodemon not detecting file changes or restarting #1115

Closed
m8r1x opened this issue Oct 13, 2017 · 8 comments
Closed

Nodemon not detecting file changes or restarting #1115

m8r1x opened this issue Oct 13, 2017 · 8 comments

Comments

@m8r1x
Copy link

m8r1x commented Oct 13, 2017 •
edited
Loading

Hi. I've seen a couple of related issues but I can't seem to find a solution in either one.
nodemon

Any help would be appreciated. 🙂
@remy
Copy link
Owner

remy commented Oct 13, 2017 via email

@m8r1x
Copy link
Author

m8r1x commented Oct 13, 2017

No not really. I didn't find any that was specific to windows 10 so I assumed that maybe I was doing something wrong. However if it's a duplicate you could close it. Sorry for any inconvenience and thanks for the reply. 🙂

@remy
Copy link
Owner

remy commented Oct 13, 2017 via email

@m8r1x
Copy link
Author

m8r1x commented Oct 13, 2017

Could you point me to some, where I can find possible solutions?

@trevorkirpaul
Copy link

trevorkirpaul commented Oct 16, 2017 •
edited
Loading

For anyone reading this that has an issue with nodemon on linux (I'm using ubuntu 16.04) make sure you installed node correctly using nvm.

I had originally installed node using the directions from the official node website (I'm sure I messed something up, since I'm new to linux) so I had to remove node using:

$ sudo apt-get remove nodejs

Then I followed the instructions found on the nvm github.

Now nodemon works perfectly. The issue was my installation method originally. If you're on linux (and new like me) then give this a try.

@kiwileaks78
Copy link

kiwileaks78 commented Nov 5, 2017 •
edited
Loading

It's a well known chokidar issue about directories with name including glob characters, like parenthesis.

Using the disableGlobbing option should solve the issue (https://github.com/browserify/watchify/pull/343).

A config option entry to add the disableGlobbing option into the chokidar config should solve this latent issue ...

@mpicard
Copy link

mpicard commented Nov 6, 2017

Still doesn't work for me, I also use ubuntu and nvm and I installed it following the instructions of nvm and do not have a system nodejs installed

@ddimitrioglo
Copy link

ddimitrioglo commented Nov 30, 2017 •
edited
Loading

Facing the same issue on macOS

P.S. Node 6 (using NVM)

remy added a commit that referenced this issue Dec 4, 2017
@remy
feat: disable chokidar globbing on windows
d05af35 
Fixes a range of issues, including:

Fixes #1115
@remy remy mentioned this issue Dec 4, 2017
Merged
@remy remy closed this as completed in #1140 Dec 4, 2017
remy added a commit that referenced this issue Dec 4, 2017
@remy
feat: disable chokidar globbing on windows (#1140)
24a4b84 
Fixes a range of issues, including:

Fixes #1115

* refactor: use Object.assign in place of merge (this will leak to more work)

Since we're now supporting 6 upwards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@remy @mpicard @ddimitrioglo @kiwileaks78 @m8r1x @trevorkirpaul