Nodemon: "watching 0 files" for "username.github.io" directories

[kenhoff]

Hey there - I'm running into some issues when running nodemon inside of a directory that's used for Github Pages and named something like username.github.io.

Adding the -V flag showed:

[nodemon] watching 0 files

After a little more experimentation, I think that the problem is the .git section of the directory name. I set up an example repo where I test username.github.io and username.gifhub.io. username.github.io watches 0 files, and username.gifhub.io watches 1 file.

If possible, I'd like a chance to fix this and submit a pull request (first OSS contribution), but I'm not really sure where to start. Any pointers?

Thanks!

(Here's nodemon --dump):

node: v5.3.0
nodemon: 1.9.1
command: /usr/local/bin/node /usr/local/bin/nodemon --dump
cwd: /Users/ken/dev/nodemon-git-issue/username.github.io
OS: darwin x64
--------------
{ run: false,
  system: { cwd: '/Users/ken/dev/nodemon-git-issue/username.github.io' },
  required: false,
  dirs: [ '/Users/ken/dev/nodemon-git-issue/username.github.io' ],
  timeout: 1000,
  options:
   { dump: true,
     ignore:
      [ '.git',
        '.nyc_output',
        '.sass-cache',
        'bower_components',
        'coverage',
        'node_modules',
        re: /\.git|\.nyc_output|\.sass\-cache|bower_components|coverage|node_modules/ ],
     watch: [ '*.*', re: /.*\..*/ ],
     ignoreRoot:
      [ '.git',
        '.nyc_output',
        '.sass-cache',
        'bower_components',
        'coverage',
        'node_modules' ],
     restartable: 'rs',
     colours: true,
     execMap: { py: 'python', rb: 'ruby' },
     stdin: true,
     runOnChangeOnly: false,
     verbose: false,
     stdout: true,
     execOptions:
      { script: null,
        exec: 'node',
        args: [],
        scriptPosition: null,
        nodeArgs: undefined,
        ext: 'js,json',
        env: {},
        execArgs: [] },
     monitor:
      [ '*.*',
        '!.git',
        '!.nyc_output',
        '!.sass-cache',
        '!bower_components',
        '!coverage',
        '!node_modules' ] },
  load: [Function],
  reset: [Function: reset],
  lastStarted: 0,
  loaded: [],
  watchInterval: null,
  command: { raw: { executable: 'node', args: [] }, string: 'node' } }
--------------

[mindvox]

I get the same in my NodeJS projects?

[kenhoff]

Yo @remy - any pointers on how I could contribute to fix this?

Thanks!

[mindvox]

@remy could this be related to #839 I have a public repo to reproduce my issue 💣

[aldum]

This seems to be breaking on all paths which contain a dot [.] character.

[zagonine]

Same problem for me. I had to rename my project folder with no dot in order to make nodemon works.

[micahbrich]

@aldum finally! I was searching high & low, couldn't figure it out — that was it! renamed to a non-dot folder name & it works 🙌

[omgimanerd]

This is quite annoying. Is there going to be a fix for this anytime soon?

[remy]

Did you send a PR? If so I can take a look.

On Fri, 22 Sep 2017, 20:00 Alvin Lin [e-mail] wrote:

This is quite annoying. Is there going to be a fix for this anytime soon?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/remy/nodemon/issues/808#issuecomment-331533189, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hAAPy85s9i4X48VJEI1tr9fXQebCks5slAPAgaJpZM4H48Bs
.

[omgimanerd]

I could do so. I really like using this package, but a lot of my projects have dots in their folder name. Before I create a fork and send a pull request though, I'd just like to confirm that this behavior is desired by the majority of users and this is the direction you want to take (I'm also very unfamiliar with this codebase). Are there any specifications to this change?

[stale[bot]]

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3