Update wait-on to the latest version 🚀

greenkeeper[bot] commented 5 years ago

The devDependency wait-on was updated from `3.2.0` to `3.3.0`.

This version 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.

Publisher: jeffbski License: MIT

Find out more about this release.

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper bot :palm_tree:

szerintedmi commented 5 years ago

Deploy preview for augmint ready!

Built with commit 915a189de18b2444dd41166cacc94eab350f7b7d

https://deploy-preview-691--augmint.netlify.com

greenkeeper[bot] commented 4 years ago

The devDependency wait-on was updated from 3.2.0 to 4.0.0.

Update to this version instead 🚀

Release Notes for v4.0.0 - a fresh approach

Rewrite of the main code to simplify the logic and reduce possibility for race conditions. Bumped the major version do to the rewrite and also a minor change in how the stability window is used. In the new version the stability window only applies to file resources (waiting for them to exist and stop changing), for other resources they are completed as soon as available.

Also in the new logic, once a resource becomes available the system doesn't continue to check it, it only continues checking the pending resources.

Logging was improved and simplified.

-l / --log just indicate what resources are still pending
-v / --verbose includes resources that are pending and debug info from checks

Updated many dependencies including rxjs, and joi. Removed core-js polyfill as no longer needed.

Added a -s / --simultaneous optional flag to the command. If provided it will limit the number of simultaneous or concurrent connections to an individual resource. It defaults to Infinity so it will make requests without caring about previous ones. If you were to set it to "1" then it wouldn't be sending new requests to http://foo before the previous one finished (success, failure, or timeout).

Commits

The new version differs by 20 commits.