Regression: nodemon not restarting, but detecting changeg

[simpss]

This seems to be a regression. It was fixed in #813 a couple months ago.

• nodemon -v: 1.17.1
• node -v: 6.13.1
• Operating system/terminal environment: debian stretch
• Command you ran: ./node_modules/.bin/nodemon --exitcrash --exec ts-node -- ./src/index.ts

Expected behaviour

nodemon should restart when a change is detected

Actual behaviour

nodemon detects the change, but doesn't actually restart the process.

[nodemon] Looking in package.json for nodemonConfig
[nodemon] 1.12.5
[nodemon] reading config /opt/packages/package/package.json
[nodemon] to restart at any time, enter `rs`
[nodemon] ignoring: .git .nyc_output .sass-cache bower_components coverage /opt/packages/package/node_modules/**/* ts-node-*/**/*
[nodemon] watching: *.*
[nodemon] watching extensions: ts
[nodemon] starting `ts-node ./src/index.ts`
[nodemon] child pid: 28
[nodemon] watching 3 files
Been Running for 0 seconds
Been Running for 1 seconds
.......
Been Running for 18 seconds
Been Running for 19 seconds
[nodemon] files triggering change check: src/index.ts
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] delaying restart for 2500ms
Been Running for 20 seconds
Been Running for 21 seconds
Been Running for 22 seconds
[nodemon] restarting due to changes...
[nodemon] src/index.ts

Been Running for 23 seconds
Been Running for 24 seconds
Been Running for 25 seconds
Been Running for 26 seconds
Been Running for 27 seconds
Been Running for 28 seconds
Been Running for 29 seconds
Been Running for 30 seconds
.....

Steps to reproduce

I've updated the reproduction sample used in #813 to use the latest nodemon version.
https://github.com/simpss/nodemon-issue-813-repro

Usage instructions in the repository readme and some more info in this comment here: #813 (comment)

---

If applicable, please append the --dump flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.

[simpss]

Turns out, silly me only updated the global version of nodemon, not the project one and made the same mistake again in the reproduction repository.