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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
fs-extra	dependencies	major	^6.0.1 -> ^11.0.0
@types/fs-extra (source)	devDependencies	major	^9.0.1 -> ^11.0.0

---

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)

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)

v9.1.0

Compare Source

• Add promise support for fs.rm() (#​841, #​860)
• Upgrade universalify for performance improvments (#​825)

v9.0.1

Compare Source

• Fix issue with ensureFile() when used with Jest on Windows (#​804, #​805)
• Remove unneeded process.umask() call (#​791)
• Docs improvements (#​753, #​795, #​797)

v9.0.0

Compare Source

Breaking changes

• Requires Node.js version 10 or greater (#​725, #​751)
• Switched ensureDir* to use a fork of https://github.com/sindresorhus/make-dir to make use of native recursive fs.mkdir where possible (#​619, #​756)
• Properly preserve atime for copy* with preserveTimestamps option (#​633)

The following changes, allthough technically breaking, will not affect the vast majority of users:

• outputJson now outputs objects as they were when the function was called, even if they are mutated later (#​702, #​768)
• Cannot pass null as an options parameter to *Json* methods (#​745, #​768)

Improvements

• Add promise shims for fs.writev & fs.opendir (#​747)
• Better errors for ensureFile (#​696, #​744)
• Better file comparison for older Node versions (#​694)

Miscellaneous changes

• Peformance optimizations (#​762, #​764)
• Add missing documentation for aliases (#​758, #​766)
• Update universalify dependency (#​767)

v8.1.0

Compare Source

• Add support for promisified fs.realpath.native in Node v9.2+ (#​650, #​682)
• Update graceful-fs dependency (#​700)
• Use graceful-fs everywhere (#​700)

v8.0.1

Compare Source

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

v8.0.0

Compare Source

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)

v7.0.1

Compare Source

• 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)

v7.0.0

Compare Source

• 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)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the fs-extra and @types/fs-extra dependencies to their latest major versions. This includes upgrading fs-extra from v6.0.1 to v11.0.0 and @types/fs-extra from v9.0.1 to v11.0.0. These updates include breaking changes, new features, bug fixes, and performance improvements.

Class diagram showing fs-extra dependency update

classDiagram
    class Dependencies {
        +fs-extra: string
        +@types/fs-extra: string
    }
    class OldVersion {
        +fs-extra: ^6.0.1
        +@types/fs-extra: ^9.0.1
    }
    class NewVersion {
        +fs-extra: ^11.0.0
        +@types/fs-extra: ^11.0.0
    }
    Dependencies <|-- OldVersion: Before
    Dependencies <|-- NewVersion: After
    note for NewVersion "Major version update with breaking changes"

Loading

State diagram for fs-extra version changes

stateDiagram-v2
    [*] --> v6.0.1: Initial
    v6.0.1 --> v11.0.0: Update
    state v11.0.0 {
        [*] --> ESMSupport: Added ESM named exports
        [*] --> NodeRequirement: Requires Node.js v14.14+
        [*] --> Performance: Improved copy performance
        [*] --> BugFixes: Various bug fixes
    }
    note right of v11.0.0: Breaking changes and new features

Loading

File-Level Changes

Change	Details	Files
Updated fs-extra dependency to v11	Updated fs-extra from ^6.0.1 to ^11.0.0 in package.json. Updated fs-extra in package-lock.json.	package.json package-lock.json
Updated @types/fs-extra dependency to v11	Updated @types/fs-extra from ^9.0.1 to ^11.0.0 in package.json. Updated @types/fs-extra in package-lock.json.	package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!