Ignore more than one events for changing the main script file

[ghost]

This PR makes it impossible to reload once app.quit() is cancelled, but it can be avoided at specifying hardResetMethod: 'exit'.

Fixes #46

[HeilTec]

This makes perfect sense.
Logical and minimal change to effect the desired function using the 'exit' method.

Still ... it would be nice if an implementation could be found that would allow all cases to work, even after canceling the 'quit' method.

Would a setTimeout be able to do the trick?

    const spawnAndQuit = () => {
      // Detaching child is useful when in Windows to let child
      // live after the parent is killed
      let child = spawn(eXecutable, [appPath], {
        detached: true,
        stdio: 'inherit'
      })
      child.unref()
      // Kamikaze!

      // In cases where an app overrides the default closing or quiting actions
      // firing an `app.quit()` may not actually quit the app. In these cases
      // you can use `app.exit()` to gracefully close the app.
      if (opts.hardResetMethod === 'exit') {
        app.exit()
      } else {
        app.quit()
      }
    }
    var resetEnqueued = null
    chokidar.watch(mainFile).on('change', () => {
        resetEnqueued && clearTimeout(resetEnqueued)
        resetEnqueued = setTimeout( () => {
          spawnAndQuit() // perhaps In-line current code directly here?
    }, 250) 

... or does the exit method cancel the timer?

[yan-foto]

Thanks! Sorry for the late reply. This sounds great! Please give me a little bit time to merge it.
@HeilTec I am usually very carefull with timeouts. But it might be worth a try.

[ghost]

@HeilTec I didn't think of using setTimeout.
That seems a good idea, but the delay value should be larger than 250ms.

I did a quick test with two Windows 10 laptops.
In one, I changed the main script once and change event is fired twice at an around 300ms interval.
In other one, it's fired three times at around 600ms intervals.

It's necessary to consider that the delay of running quit method depends to PC performance.

[yan-foto]

I really suck at maintaining projects! More than 2 months for a simple merge 🙈 Sorry everyone!

[mscoobby]

Is this going to be released as it's not in 1.4.0? Also consider #57 these two fixes many of the hardReset problems.

[yan-foto]

@mscoobby in v1.4.0 instead of having two separate watchers (one for the main file and another for the rest), there is a single watcher. It is due to many requests from people wanting to have hard resets for every change and not only the main file.

[mscoobby]

@yan-foto yes but using hardWatcher.on(... instead of hardWatcher.once(.. causes it to spawn 2 processes as pointed out in #46