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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fs-extra	^10.0.0 -> ^11.3.0
fs-extra	^10.0.1 -> ^11.3.0
@types/fs-extra (source)	^9.0.12 -> ^11.0.4
@types/fs-extra (source)	^9.0.13 -> ^11.0.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

jprichardson/node-fs-extra (fs-extra)

v11.3.0

Compare Source

• Add promise support for newer fs methods (#​1044, #​1045)
• Use fs.opendir in copy()/copySync() for better perf/scalability (#​972, #​1028)

v11.2.0

Compare Source

• Copy directory contents in parallel for better performance (#​1026)
• Refactor internal code to use async/await (#​1020)

v11.1.1

Compare Source

• Preserve timestamps when moving files across devices (#​992, #​994)

v11.1.0

Compare Source

• Re-add main field to package.json for better TypeScript compatibility (#​979, #​981)

v11.0.0

Compare Source

Breaking Changes

• Don't allow requiring fs-extra/lib/SOMETHING (switched to exports) (#​974)
• Require Node v14.14+ (#​968, #​969)

New Features

• Add fs-extra/esm for ESM named export support; see docs for details (#​746, #​974)
• Add promise support for fs.readv() (#​970)

Bugfixes

• Don't stat filtered items in copy* (#​965, #​971)
• Remove buggy stats check in copy (#​918, #​976)

v10.1.0

Compare Source

• Warn if fs.realpath.native does not exist, instead of erroring (#​953)
• Allow explicitly passing undefined options to move() (#​947, #​955)
• Use process.emitWarning instead of console.warn (#​954)

v10.0.1

Compare Source

• Add sideEffects: false to package.json (#​941)

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: packages/typescript/vue3-vben-admin/boilerplate/tests/server/yarn.lock

error This project's package.json defines "packageManager": "yarn@[email protected]". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.