events has wrong timing and order when using -C (--on-change-only)

[GongT]

[root@localhost tmp]# nodemon -C --config ./nodemon.json --exec /bin/sh -c "echo 'really started' ; sleep 1000"
[nodemon] 1.11.0
[nodemon] to restart at any time, enter rs
[nodemon] watching: wow.json
start!!!!　　　　　　　　　　<-but nothing started

nodemon wait here, run touch wow.json in another terminal

[nodemon] restarting due to changes...
[nodemon] starting /bin/sh -c "echo 'really started' ; sleep 1000"
really started
start!!!!
restart　　　　　　　　　　<-restart after start 😂I spend so many time to find this bug

nodemon wait here, run touch wow.json in another terminal

[nodemon] restarting due to changes...
restart
[nodemon] starting /bin/sh -c "echo 'really started' ; sleep 1000"
really started
start!!!!

If I trigger more change, the output will same as the last block quote.

The last part is right, first 2 is wrong...

It's also right without -C option.

[remy]

Um, where does start!!! come from? I can't see it anywhere in the command you're running. Can you share your nodemon.json file too?

[GongT]

oh...i forgot it... sorry...

{
        "events": {
                "start": "echo 'start!!!!'",
                "restart": "echo restart"
        },
        "restartable": "rs",
        "watch": "wow.json"
}

[remy]

I'd hazard a guess that the event is firing outside of the conditional that says don't run the command upon startup.

[stale]

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