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 (5)
refactor(deps): Pin Dependencies Branch name: renovate/pin-dependencies Pins @​types/graphql in optionalDependencies from ^0.9.0 to 0.9.4 Pins @​types/async in optionalDependencies from ^2.0.31 to 2.0.40 Pins webpack-bundle-analyzer in devDependencies from ^2.4.0 to 2.8.3 Pins webpack in devDependencies from ^3.0.0 to 3.4.1 Pins uglify-js in devDependencies from ^3.0.16 to 3.0.27 Pins typescript in devDependencies from ~2.4.1 to 2.4.2 Pins tslint in devDependencies from ^5.5.0 to 5.5.0 Pins ts-jest in devDependencies from ^20.0.7 to 20.0.7 Pins source-map-support in devDependencies from ^0.4.0 to 0.4.15 Pins sinon in devDependencies from ^2.1.0 to 2.4.1 Pins rxjs in devDependencies from ^5.0.0-beta.11 to 5.4.2 Pins rollup in devDependencies from ^0.45.2 to 0.45.2 Pins request in devDependencies from ^2.75.0 to 2.81.0 Pins pretty-bytes in devDependencies from ^4.0.0 to 4.0.2 Pins prettier in devDependencies from ^1.5.2 to 1.5.3 Pins pre-commit in devDependencies from ^1.2.2 to 1.2.2 Pins nodemon in devDependencies from ^1.11.0 to 1.11.0 Pins mocha in devDependencies from ^3.0.0 to 3.4.2 Pins minimist in devDependencies from ^1.2.0 to 1.2.0 Pins lodash in devDependencies from ^4.17.1 to 4.17.4 Pins lint-staged in devDependencies from ^4.0.1 to 4.0.2 Pins istanbul in devDependencies from ^0.4.5 to 0.4.5 Pins isomorphic-fetch in devDependencies from ^2.2.1 to 2.2.1 Pins gzip-size in devDependencies from ^3.0.0 to 3.0.0 Pins grunt-tslint in devDependencies from ^5.0.1 to 5.0.1 Pins flow-bin in devDependencies from ^0.50.0 to 0.50.0 Pins fetch-mock in devDependencies from ^5.10.0 to 5.12.1 Pins es6-promise in devDependencies from ^4.0.4 to 4.1.1 Pins danger in devDependencies from ^1.0.0 to 1.1.0 Pins concurrently in devDependencies from ^3.1.0 to 3.5.0 Pins colors in devDependencies from ^1.1.2 to 1.1.2 Pins chai-as-promised in devDependencies from ^7.0.0 to 7.1.1 Pins chai in devDependencies from ^4.0.2 to 4.1.0 Pins bundlesize in devDependencies from ^0.13.0 to 0.13.2 Pins browserify in devDependencies from ^14.3.0 to 14.4.0 Pins benchmark in devDependencies from ^2.1.3 to 2.1.4 Pins @​types/sinon in devDependencies from ^2.1.0 to 2.3.3 Pins @​types/mocha in devDependencies from ^2.2.31 to 2.2.41 Pins @​types/benchmark in devDependencies from ^1.0.30 to 1.0.30
chore(deps): Update dependency @​types/node to version 8.0.17 Branch name: renovate/@types/node-8.x Upgrades @​types/node in devDependencies from 8.0.14 to 8.0.17
chore(deps): Update dependency flow-bin to version 0.51.1 Branch name: renovate/flow-bin-0.x Upgrades flow-bin in devDependencies from ^0.50.0 to 0.51.1
chore(deps): Update dependency remap-istanbul to version 0.9.5 Branch name: renovate/remap-istanbul-0.x Upgrades remap-istanbul in devDependencies from 0.8.0 to 0.9.5
chore(deps): Update dependency @​types/graphql to version 0.10.1 Branch name: renovate/@types/graphql-0.x Upgrades @​types/graphql in optionalDependencies from ^0.9.0 to 0.10.1

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.

[apollo-cla]

@renovate[bot]: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[apollo-cla]

	Messages
📖	Please add your name and email to the AUTHORS file (optional)
📖	If this was a change that affects the external API, please update the docs and post a link to the PR in the discussion

Generated by 🚫 dangerJS

[stubailo]

CLA fixed!