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

Update concurrently to the latest version 🚀 #43

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Aug 24, 2018

Version 4.0.0 of concurrently was just published.

Dependency concurrently
Current Version 3.6.1
Type devDependency

The version 4.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of concurrently.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Release Notes v4.0.0

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.

Commits

The new version differs by 28 commits.

  • 3690676 4.0.0
  • b4e414c npm: update and remove some deps
  • 4043fc2 Exit gracefully on SIGINT (#164)
  • b1daf8d logger: show no prefix when the format is none
  • 58d7d97 Take options such as prefixLength and outputStream
  • 1d0598a docs: add programmatic API usage
  • 571671b Add missing export of LogExit
  • 7ac9b6e Remove unused RxJS schedulers
  • caa23b3 bin: change tested exit code to 1 on Windows (#163)
  • bfd7501 ci: run AppVeyor on Node 10
  • adcc0b5 Merge pull request #157 from kimmobrunfeldt/v4
  • 0e60d2d docs: move the why section to the top
  • b136183 docs: update help section
  • c127d92 Add support for prefix length (#162)
  • daddad1 bin: don't check order of lines emitted

There are 28 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 🌴

greenkeeper bot added a commit that referenced this pull request Aug 26, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 26, 2018

Version 4.0.1 just got published.

Update to this version instead 🚀

Commits

The new version differs by 3 commits.

  • b4c0894 4.0.1
  • 0b3d806 bin: delay command in test that should be successful
  • a9ef086 Make success condition use exiting order, as per docs

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant