Bump rollup-plugin-node-resolve from 4.2.4 to 5.2.0

[dependabot-preview]

Bumps rollup-plugin-node-resolve from 4.2.4 to 5.2.0.

Changelog

Sourced from rollup-plugin-node-resolve's changelog.

5.2.0 (2019-06-29)

• dedupe accepts a function (#225 by @​manucorporat)

5.1.1 (2019-06-29)

• Move Rollup version check to buildStart hook to avoid issues (#232 by @​lukastaegert)

5.1.0 (2019-06-22)

• Fix path fragment inputs (#229 by @​bterlson)

5.0.4 (2019-06-22)

• Treat sideEffects array as inclusion list (#227 by @​mikeharder)

5.0.3 (2019-06-16)

• Make empty.js a virtual module (#224 by @​manucorporat)

5.0.2 (2019-06-13)

• Support resolve 1.11.1, add built-in test (#223 by @​bterlson)

5.0.1 (2019-05-31)

• Update to resolve@1.11.0 for better performance (#220 by @​keithamus)

5.0.0 (2019-05-15)

• Replace bublé with babel, update dependencies (#216 by @​mecurc)
• Handle module side-effects (#219 by @​lukastaegert)

Breaking Changes

• Requires at least rollup@1.11.0 to work (v1.12.0 for module side-effects to be respected)
• If used with rollup-plugin-commonjs, it should be at least v10.0.0

Commits

• 07b00d0 5.2.0
• be9d14b Update changelog
• df90657 feat(): dedupe accepts a function (#225)
• 3a8ebf1 5.1.1
• f054cf1 Update changelog
• 02f0e6d Move Rollup version check to buildStart hook to avoid issues because (#232)
• 84471e4 Use async fs methods (#230)
• 4b1e355 5.1.0
• fc69994 Update changelog
• f3c8320 Fix path fragment inputs (#229)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes a major update to a development dependency.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)