Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
fs-extra 11.2.0 -> 11.3.0 age adoption passing confidence

Release Notes

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

v11.3.0

Compare Source

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

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

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

v9.1.0

Compare Source

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

v9.0.1

Compare Source

v9.0.0

Compare Source

Breaking changes

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

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)

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Feb 12, 2025

⚠️ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vue-tsc
npm ERR!   vue-tsc@"^1.8.27" from [email protected]
npm ERR!   node_modules/vite-plugin-dts
npm ERR!     dev vite-plugin-dts@"3.9.1" from @3squared/[email protected]
npm ERR!     packages/ui
npm ERR!       @3squared/[email protected]
npm ERR!       node_modules/@3squared/forge-ui
npm ERR!         workspace packages/ui from the root project
npm ERR!         2 more (@3squared/forge-playground, forge-ui-styleguide)
npm ERR!   dev vue-tsc@"1.8.27" from @3squared/[email protected]
npm ERR!   packages/playground
npm ERR!     @3squared/[email protected]
npm ERR!     node_modules/@3squared/forge-playground
npm ERR!       workspace packages/playground from the root project
npm ERR!       1 more (forge-ui-styleguide)
npm ERR!   2 more (@3squared/forge-ui, forge-ui-styleguide)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional vue-tsc@"~2.1.6" from [email protected]
npm ERR! node_modules/vite-plugin-checker
npm ERR!   dev vite-plugin-checker@"0.8.0" from [email protected]
npm ERR!   apps/docs
npm ERR!     [email protected]
npm ERR!     node_modules/forge-ui-styleguide
npm ERR!       workspace apps/docs from the root project
npm ERR!   dev vite-plugin-checker@"0.8.0" from @3squared/[email protected]
npm ERR!   packages/ui
npm ERR!     @3squared/[email protected]
npm ERR!     node_modules/@3squared/forge-ui
npm ERR!       workspace packages/ui from the root project
npm ERR!       2 more (@3squared/forge-playground, forge-ui-styleguide)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/vue-tsc
npm ERR!   peerOptional vue-tsc@"~2.1.6" from [email protected]
npm ERR!   node_modules/vite-plugin-checker
npm ERR!     dev vite-plugin-checker@"0.8.0" from [email protected]
npm ERR!     apps/docs
npm ERR!       [email protected]
npm ERR!       node_modules/forge-ui-styleguide
npm ERR!         workspace apps/docs from the root project
npm ERR!     dev vite-plugin-checker@"0.8.0" from @3squared/[email protected]
npm ERR!     packages/ui
npm ERR!       @3squared/[email protected]
npm ERR!       node_modules/@3squared/forge-ui
npm ERR!         workspace packages/ui from the root project
npm ERR!         2 more (@3squared/forge-playground, forge-ui-styleguide)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-03-11T01_25_26_563Z-debug-0.log

Copy link

changeset-bot bot commented Feb 12, 2025

⚠️ No Changeset found

Latest commit: d8a0a4a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/fs-extra-11.x branch from 4a1154a to d8a0a4a Compare March 11, 2025 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants