Configure Renovate

[renovate]

Welcome to Renovate!

This is an onboarding PR to help you understand and configure Renovate before any regular Pull Requests begin. Once you close this Pull Request, Renovate will begin keeping your dependencies up-to-date via automated Pull Requests.

If you have any questions, try reading our Getting Started Configuring Renovate page first.

---

With your current configuration, renovate will initially create the following Pull Requests:

Pull Requests (8)
Update dependency for-in to version ~1.0.0 Branch name: renovate/for-in-1.x Upgrades for-in in dependencies from ~0.1.4 to ~1.0.0
Update dependency is-match to version ~0.4.0 Branch name: renovate/is-match-0.x Upgrades is-match in dependencies from ~0.2.0 to ~0.4.0
Update dependency is-match to version ~1.0.0 Branch name: renovate/is-match-1.x Upgrades is-match in dependencies from ~0.2.0 to ~1.0.0
Update dependency object.reduce to version ~1.0.0 Branch name: renovate/object.reduce-1.x Upgrades object.reduce in dependencies from ~0.1.7 to ~1.0.0
Pin Dependencies Branch name: renovate/pin-dependencies Pins kind-of in devDependencies from ^2.0.0 to 2.0.1 Pins assertit in devDependencies from ^0.1.0 to 0.1.0
Update dependency kind-of to version 3.x Branch name: renovate/kind-of-3.x Upgrades kind-of in devDependencies from ^2.0.0 to 3.2.2
Update dependency kind-of to version 4.x Branch name: renovate/kind-of-4.x Upgrades kind-of in devDependencies from ^2.0.0 to 4.0.0
Update dependency kind-of to version 5.x Branch name: renovate/kind-of-5.x Upgrades kind-of in devDependencies from ^2.0.0 to 5.0.0

Sometimes you may see multiple options for the same dependency (e.g. pinning in one branch and upgrading in another). This is expected and allows you the flexibility to choose which to merge first. Once you merge any PR, others will be updated or removed the next time Renovate runs.

Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch and this Pull Request description will be updated the next time Renovate runs.

Our Configuration Docs should be helpful if you wish to modify any behaviour.

---

Don't want a renovate.json file?

You are not required to merge this Pull Request - Renovate will begin even if this "Configure Renovate" PR is closed unmerged and without a renovate.json file. However, it's recommended that you add configuration to your repository to ensure behaviour matches what you see described here.

Alternatively, you can add the same configuration settings into a "renovate" section of your package.json file(s) in this branch and delete the renovate.json from this PR. If you make these configuration changes in this branch then the results will be described in this PR after the next time Renovate runs.

[coveralls]

Coverage remained the same at 100.0% when pulling a91250e on renovate/configure into 601e02e on master.

[coveralls]

Coverage remained the same at 100.0% when pulling a91250e on renovate/configure into 601e02e on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 719576d on renovate/configure into 601e02e on master.