Update dependency concurrently to v4

[renovate]

This Pull Request updates devDependency concurrently (source) from v3.6.1 to v4.0.0

Release Notes

v4.0.0

Compare Source
More than anything, v4 is just a big refactor to allow changes to be made faster and more reliably.
It does feature some small breaking changes, and maybe even fixes some longstanding bugs.

Breaking changes

• The CLI option --allow-restarts is no more.
  Instead, just set --restart-tries to something greater than 0.
• Input handling is now opt-in via --handle-input flag. (#​147)
  It does come with some specific input parsing that would make it difficult for you to use it.
• Setting prefix to none will now actually not prefix commands' outputs.
  Previously, it would prefix with [].
• SIGINTs/Ctrl+C will now be handled gracefully. (#​150)
  No more exiting with code 1 or tweaking --success flag.

No more null exit codes (#​133)

That's a pretty bad bug that existed till now. You won't see a log like this anymore:

[1] npm run lint-watch exited with code null

What you will see going forward is the actual exit signal:

[1] npm run lint-watch exited with code SIGTERM

concurrently finally gets a shiny ✨ programmatic API!

Closes #​101, #​112. Maybe even #​103.

const concurrently = require('concurrently');
await concurrently([
    'npm:watch-*',
    { name: 'server', command: 'nodemon' }
], {
  prefix: 'name',
  killOthers: ['failure'],
  restartTries: 3
});

Check the docs here for some info on how to use it.

---

---

This PR has been generated by Renovate Bot.

[coveralls]

Coverage remained the same at 100.0% when pulling e9d9665 on renovate/concurrently-4.x into 7fc3c15 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e9d9665 on renovate/concurrently-4.x into 7fc3c15 on master.