Update dependency wait-on to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wait-on	4.0.2 -> 6.0.1

---

Release Notes

jeffbski/wait-on

v6.0.1

Compare Source

Updated minor dependencies to fix vulnerabilities

v6.0.0

Compare Source

Other than dropping support for Node.js v8 there should be no other breaking changes.

Node.js v8 was no longer supported by the yargs parser. Node.js v8 users should use v5.3.0

v5.3.0

Compare Source

Allow resources to be passed in via config file. Thanks @​michaelmerrill for the PR.

Example config.js file with resources

module.exports = {
  resources: ['http://localhost:8123', 'http://localhost:8123/foo'],
};

v5.2.2

Compare Source

Updated [email protected]

Updated lodash dependency to close vulnerability

v5.2.1

Compare Source

Update dependencies

v5.2.0

Compare Source

• expose the remaining resources in the timeout error message (thanks @​jmealo)
• update from the deprecated @hapi/joi to joi (thanks @​AleF83)

v5.1.0

Compare Source

Add proxy option which can override the http(s) proxy which might be configured in environment variables.

• opts.proxy: undefined, false, or object as defined in axios. Default is undefined. If not set (undefined) axios detects proxy from env vars http_proxy and https_proxy. https://github.com/axios/axios#config-defaults

  // example proxy object
  {
    host: '127.0.0.1',
    port: 9000,
    auth: {
      username: 'mikeymike',
      password: 'rapunz3l'
    }
  }

v5.0.3

Compare Source

update to [email protected]

v5.0.2

Compare Source

[email protected] update which resolved some potential lodash vulnerabilities

v5.0.1

Compare Source

Force axios to use http adapter to keep logs clean if jest/jsdom are used with the wait-on API.

If jest/jsdom is used then a polyfill for xhr is created which will cause axios to default the adapter to it. Since jsdom logs all errors use of wait-on will have any failed attempts to connect logged which is rather noisy and misleading.

By forcing axios to use the node.js http adapter instead this problem is bypassed keeping logs clean.

v5.0.0

Compare Source

Switch HTTP client from request to axios

Since the request package is no longer receiving updates, wait-on switched to using axios. Attempt to keep the same wait-on options as much as possible.

These breaking changes occurred in the switch:

1. There is only one option for redirects followRedirect: true|false (defaults to true).
2. httpSignature is not implemented in axios and now not available. (If this feature is still desired, please help by providing a pull request to implement it.)
3. auth allows only username and password but not the previous aliases user and pass

add optional validateStatus fn property

If validateStatus property is provided in the
config and set to a function, it will use this to
validate whether a status is valid.

The default validateStatus if not provided is

validateStatus: function (status) {
  return status >= 200 && status < 300;
}

To also allow a 401 unauthorized as a valid status

validateStatus: function (status) {
  return status === 401 || (status >= 200 && status < 300);
}

---

Configuration

📅 Schedule: "every weekend" in timezone America/New_York.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.