[Snyk] Upgrade fs-extra from 3.0.1 to 11.2.0

[q1blue]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade fs-extra from 3.0.1 to 11.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

Warning: This is a major version upgrade, and may be a breaking change.

• The recommended version is 22 versions ahead of your current version.
• The recommended version was released 2 months ago, on 2023-11-28.

Release notes

Package name: fs-extra

• 11.2.0 - 2023-11-28
  

  11.2.0

• 11.1.1 - 2023-03-20
  

  11.1.1

• 11.1.0 - 2022-11-29
  

  11.1.0

• 11.0.0 - 2022-11-28
  

  11.0.0

• 10.1.0 - 2022-04-16
  

  10.1.0

• 10.0.1 - 2022-02-22
  

  10.0.1

• 10.0.0 - 2021-05-03
  

  10.0.0

• 9.1.0 - 2021-01-19
  

  9.1.0

• 9.0.1 - 2020-06-04
  

  9.0.1

• 9.0.0 - 2020-03-19
  

  9.0.0

• 8.1.0 - 2019-06-28
• 8.0.1 - 2019-05-13
• 8.0.0 - 2019-05-11
• 7.0.1 - 2018-11-07
• 7.0.0 - 2018-07-17
• 6.0.1 - 2018-05-09
• 6.0.0 - 2018-05-01
• 5.0.0 - 2017-12-11
• 4.0.3 - 2017-12-05
• 4.0.2 - 2017-09-12
• 4.0.1 - 2017-07-31
• 4.0.0 - 2017-07-14
• 3.0.1 - 2017-05-04

from fs-extra GitHub release notes

Commit messages

Package name: fs-extra

• 5d4bf0b 11.2.0
• d293448 perf: copy dir contents in parallel (Update socket.io dependency BrowserSync/browser-sync#1026)
• a277cbb Refactor `move` API to async/await (Feature Request: RewriteRules with dom manipulation instead of regexp BrowserSync/browser-sync#1025)
• 40c5161 Refactor `copy` API to async/await (BrowserSync not available from local network after installing VirtualBox (Windows 10) BrowserSync/browser-sync#1021)
• 6f2b2bc Refactor `create*`/`ensure*` API to async/await (Source hostname:port rewriting clobbers attributes when using simple hostname BrowserSync/browser-sync#1023)
• 426bb46 Refactor `outputFile` API to async/await (CLI --files option only watches first path BrowserSync/browser-sync#1024)
• 47bc43d Simplify reduce for checking match (Unable to use browserSync with custom server. BrowserSync/browser-sync#1016)
• cc7b3b2 11.1.1
• 055e0b8 Unify cross-device move test configuration/logic (Is it possible to inject js without full reload? BrowserSync/browser-sync#1001)
• 0e7de32 Preserve timestamp when moving across devices (Browser Sync in iframe using local content? BrowserSync/browser-sync#994)
• f3a7f0b Fix build status badge (Rewrite broken for protocol-relative URLs BrowserSync/browser-sync#991)
• 2b5c083 Harden ci.yml permissions (Can't open a custom url BrowserSync/browser-sync#985)
• 0e76a72 11.1.0
• ab86a8a Re-add package.json main field for TypeScript support (Infinite event loops BrowserSync/browser-sync#981)
• 8e7793b Update action versions (Tunnel Issue on reload() BrowserSync/browser-sync#978)
• 4daff17 11.0.0
• fd50986 BREAKING: ESM support (Can't override default browser  BrowserSync/browser-sync#974)
• 1a3205d Remove unneeded and buggy stats check (lodash@4.0.0 BrowserSync/browser-sync#976)
• b3146f0 Run copy*() filter before running fs.stat() on items (Remote server Browser-sync using Internal Network's IP address rather that the External IP BrowserSync/browser-sync#971)
• 1d1622b Upgrade devDeps (#970 Fix: Change SHA-1 to SHA-256 cert BrowserSync/browser-sync#975)
• 9dbf173 Add promise support for fs.readv (SSL Self signed certificate BrowserSync/browser-sync#970)
• 5623ba3 BREAKING: Drop Node v12 support; require v14.14+ (HTTP Basic Auth BrowserSync/browser-sync#969)
• 656545c Remove sketchy citebite links in documentation (Can we sync mouse pointer? BrowserSync/browser-sync#973)
• 0220eac 10.1.0

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3a731a2

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.

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