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.

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

Nodemon does not restart on VM sync folder #1730

Closed
antoniuslin opened this issue Jun 18, 2020 · 3 comments
Closed

Nodemon does not restart on VM sync folder #1730

antoniuslin opened this issue Jun 18, 2020 · 3 comments
Labels
stale no activity for 2 weeks

Comments

@antoniuslin
Copy link

Hello,

First of all, I'm not sure if this is an issue similar to #1630, or even a nodemon issue for that matter. Imo, it's different enough that I think I should ask the community here.

Thanks in advance for your time & input.

Antonius


The materials are:

  • Host: Mac Catalina (but I've observed the same issue in other host-guest OS combo)
  • Guest: Ubuntu 18.x
  • VM: Virtual Box
  • Example Sync folder: /Users/host_username/folder/js_files to /home/guest_username/folder/js_files

The particular issue is:
When I run $> nodemon /home/username/folder/index.js then make a change (a simple re-save or add a new line suffices) to a file local to the guest environment, eg: $> vim /home/guest_username/folder/another.js, nodemon works as expected and would restart.

But if I were to make a change to a file local to the host environment, eg: $> vim /Users/host_username/folder/another.js, nodemon that's still running in guest earlier wouldn't restart.

Yet the file change is correctly reflected from the perspective of the guest user, ie, have a new file timestamp, making me believe it's not a sync folder problem. So could this be a nodemon issue?

$ nodemon --dump
[nodemon] 2.0.4
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
--------------
node: v12.18.0
nodemon: 2.0.4
command: /home/vagrant/.nvm/versions/node/v12.18.0/bin/node /home/vagrant/.nvm/versions/node/v12.18.0/bin/nodemon --dump
cwd: /home/vagrant/workspace/app
OS: linux x64
--------------
{
  run: false,
  system: { cwd: '/home/vagrant/workspace/app' },
  required: false,
  dirs: [ '/home/vagrant/workspace/app' ],
  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: /.*\..*/ ],
    monitor: [
      '*.*',
      '!**/.git/**',
      '!**/.nyc_output/**',
      '!**/.sass-cache/**',
      '!**/bower_components/**',
      '!**/coverage/**',
      '!**/node_modules/**'
    ],
    ignoreRoot: [
      '**/.git/**',
      '**/.nyc_output/**',
      '**/.sass-cache/**',
      '**/bower_components/**',
      '**/coverage/**',
      '**/node_modules/**'
    ],
    restartable: 'rs',
    colours: true,
    execMap: { py: 'python', rb: 'ruby', ts: 'ts-node' },
    stdin: true,
    runOnChangeOnly: false,
    verbose: false,
    signal: 'SIGUSR2',
    stdout: true,
    watchOptions: {},
    execOptions: {
      script: 'index.js',
      exec: 'node',
      args: [],
      scriptPosition: 0,
      nodeArgs: undefined,
      execArgs: [],
      ext: 'js,mjs,json',
      env: {}
    }
  },
  load: [Function],
  reset: [Function: reset],
  lastStarted: 0,
  loaded: [],
  watchInterval: null,
  signal: 'SIGUSR2',
  command: {
    raw: { executable: 'node', args: [ 'index.js' ] },
    string: 'node index.js'
  }
}
--------------
@stale
Copy link

stale bot commented Jul 3, 2020

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

@stale stale bot added the stale no activity for 2 weeks label Jul 3, 2020
@antoniuslin
Copy link
Author

bump

@stale stale bot removed the stale no activity for 2 weeks label Jul 8, 2020
@stale
Copy link

stale bot commented Jul 25, 2020

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

@stale stale bot added the stale no activity for 2 weeks label Jul 25, 2020
@stale stale bot closed this as completed Aug 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale no activity for 2 weeks
Projects
None yet
Development

No branches or pull requests

1 participant