Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

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

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
fs-extra 8.1.0 -> 11.1.1 age adoption passing confidence

Release Notes

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

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

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 this update again.


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

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

@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

⚠ 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
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants