Skip to content

Conversation

@angular-robot
Copy link
Contributor

This PR contains the following updates:

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

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

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, 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 has been generated by Renovate Bot.

See associated pull request for more information.
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels May 22, 2025
@angular-robot angular-robot requested a review from a team as a code owner May 22, 2025 05:04
@angular-robot angular-robot requested review from crisbeto and wagnermaciel and removed request for a team May 22, 2025 05:04
@mmalerba mmalerba added target: patch This PR is targeted for the next patch release target: rc This PR is targeted for the next release-candidate and removed target: patch This PR is targeted for the next patch release labels May 22, 2025
@mmalerba mmalerba merged commit 27b79b4 into angular:main May 22, 2025
32 checks passed
mmalerba pushed a commit that referenced this pull request May 22, 2025
See associated pull request for more information.

(cherry picked from commit 27b79b4)
@angular-robot angular-robot deleted the ng-renovate/fs-extra-11-x branch May 22, 2025 16:40
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants