Update fs-extra requirement from ^7.0.0 to ^8.0.1

[dependabot-preview]

Updates the requirements on fs-extra to permit the latest version.

Changelog

Sourced from fs-extra's changelog.

8.0.1 / 2019-05-13

• Fix bug Maximum call stack size exceeded error in util/stat (#679)

8.0.0 / 2019-05-11

NOTE: Node.js v6 support is deprecated, and will be dropped in the next major release.

• Use renameSync() under the hood in moveSync()
• Fix bug with bind-mounted directories in copy*() (#613, #618)
• Fix bug in move() with case-insensitive file systems
• Use fs.stat()'s bigint option in copy*() & move*() where possible (#657)

7.0.1 / 2018-11-07

• Fix removeSync() on Windows, in some cases, it would error out with ENOTEMPTY (#646)
• Document mode option for ensureDir*() (#587)
• Don't include documentation files in npm package tarball (#642, #643)

7.0.0 / 2018-07-16

• BREAKING: Refine copy*() handling of symlinks to properly detect symlinks that point to the same file. (#582)
• Fix bug with copying write-protected directories (#600)
• Universalify fs.lchmod() (#596)
• Add engines field to package.json (#580)

6.0.1 / 2018-05-09

• Fix fs.promises ExperimentalWarning on Node v10.1.0 (#578)

6.0.0 / 2018-05-01

• Drop support for Node.js versions 4, 5, & 7 (#564)
• Rewrite move to use fs.rename where possible (#549)
• Don't convert relative paths to absolute paths for filter (#554)
• copy*'s behavior when preserveTimestamps is false has been OS-dependent since 5.0.0, but that's now explicitly noted in the docs (#563)
• Fix subdirectory detection for copy* & move* (#541)
• Handle case-insensitive paths correctly in copy* (#568)

5.0.0 / 2017-12-11

Significant refactor of copy() & copySync(), including breaking changes. No changes to other functions in this release.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by manidlou, a new releaser for fs-extra since your current version.

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 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #377.