fix(deps): update dependency fs-extra to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fs-extra	^9.1.0 -> ^10.0.0

---

Release Notes

jprichardson/node-fs-extra

v10.0.0

Compare Source

Breaking changes

• Require Node.js v12+ (#​886, #​893, #​890, #​894, #​895)
• Allow copying broken symlinks (#​779, #​765, #​638, #​761)

The following changes, although technically semver-major, will not affect the vast majority of users:

• Ensure correct type when destination exists for ensureLink*()/ensureSymlink*() (#​826, #​786, #​870)
• Error when attempting to copy*() unknown file type (#​880)
• Remove undocumented options for remove*() (#​882)

Improvements

• Allow changing case of filenames with move*(), even on technically case-insensitive filesystems (#​759, #​801)
• Use native fs.rm*() for remove*() in environments that support it (#​882, #​806)
• Improve emptyDir() performance (#​885)

Bugfixes

• Ensure copy*()'s filter function is not called more than necessary (#​883, #​809)
• Fix move*() raising EPERM error when moving a file to the root of a drive on Windows (#​897, #​819)

Miscellaneous changes

• Do not use at-least-node as a dependency (#​896)
• Improve documentation (#​888, #​830, #​884, #​843)

---

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 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, check this box.

---

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

[lindsaylevine]

this requires node 12+ - @erezrokah when's safe to drop support for node 10 you think?

[erezrokah]

I see several options:

1. You can drop Node.js 10 support (behind a major version) and use the compatibility field like the Lighthouse plugin:
   https://github.com/netlify/plugins/blob/99232ce2096d3db7e27f0f1f62a3f3dd34e2c18d/site/plugins.json#L364
2. Wait for us to drop Node.js 10 support, @JGAntunes is currently working on dropping Node.js 8. I don't think we have a definitive timeline yet
3. Remove the usage of fs-extra from codebase. From https://github.com/netlify/netlify-plugin-nextjs/search?p=1&q=fs-extra I don't see a very compelling reason to keep it, but I might be missing something

Personally I prefer 3.

[ascorbic]

We're going to hold off on this until we can drop Node 10, which we'll do when Next does

[ascorbic]

Let's close this PR. We can get do the upgrade manually when we drop Node 10

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 10.x releases. However, if you upgrade to 10.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

[erezrokah]

Opened a follow up PR #452 so revovate stops bugging on future updates