[Snyk] Security upgrade fast-glob from 2.2.1 to 3.3.3

[Omrisnyk]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• large-file/package.json
• large-file/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	169
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	124

Release notes

Package name: fast-glob

• 3.3.3 - 2025-01-05
  

  Full Changelog: 3.3.2...3.3.3

  💬 Common

  • Refer to [email protected] to avoid annoying npm audit spam (#443, #444, #454, #456, #457, #461)

  🐛 Bug fixes

  • Apply absolute negative patterns to full path instead of file path (#441, thanks @ webpro)
• 3.3.2 - 2023-11-06
  

  Full Changelog: 3.3.1...3.3.2

  🐛 Bug fixes

  • Handle square brackets as a special character on Windows in escape functions (#425)
  • Keep escaping after brace expansion (#422)
• 3.3.1 - 2023-07-22
  

  Full Changelog: 3.3.0...3.3.1

  This release fixes a regression for cases where the ignore option is used with a string (#403, #404).

  The public interface of this package does not support a string as the value for the ignore option since 2018 year (release).

  So, in the next major release, we will reintroduce method implementations that do not involve strings in the ignore option.

• 3.3.0 - 2023-06-30
  

  Full Changelog: 3.2.12...3.3.0

  🚀 Improvements

  Method aliases

  New methods (glob, globSync, globStream) have been added in addition to the current methods (default import, sync, stream), which eliminate the need to rename the method when importing. In addition, an async alias has been added for the default import, which makes it possible to use this packet with ESM.

  Method to convert paths to globs

  A new method (convertPathToPattern) has been added in this release to convert a path to a pattern. The primary goal is to enable users to avoid processing Windows paths in each location where this package is used by utilities from third-party packages.

  See more details in the pull request.

  🐛 Bug fixes

  • In the past, we mishandled patterns that contained slashes when the baseNameMatch option was enabled, which went against the documented behavior. (#312)
  • Several problems with matching patterns that contain brace expansion have been resolved. The primary issue solved is when the pattern has duplicate slashes after it is expanded (#394), or the micromatch package does not correctly generate a regular expression (#365).
  • All negative patterns will now have the dot option enabled when matching paths. Previously, the !**/* patterns did not exclude hidden files (start with a dot). (#343)
  • The issue that led to duplicates in the results when overlapping or duplicate patterns were present among the patterns has been fixed. At the moment, we are only talking about leading dot. Other cases are not included. For example, running with the patterns ['./file.md', 'file.md', '*'] will now only include file.md once in the results. (#190)

  📖 Documentation

  A clarifying note has been added for the concurrency option, which provides more detailed information about the Thread Pool utilization.

  ⚙️ Infrastructure

  • The benchmark in CI is now running on Node.js 20.
  • The benchmark now uses the public package bencho instead of an in-house implementation. You may want to try this solution for your packages and provide feedback.

  🥇 New Contributors

  • @ josh-hemphill made their first contribution in #383
  • @ mairaw made their first contribution in #401
• 3.2.12 - 2022-09-09
  

  Full Changelog: 3.2.11...3.2.12

  🐛 Bug fixes

  Fixed an issue introduced in 3.2.7 related to incorrect application of patterns to entries with a trailing slash when the entry is not a directory.

  Before changes:

  fg.sync('**/!(*.md)')
  // ['file.md', 'a/file.md', 'a/file.txt']

  After fix:

  fg.sync('**/!(*.md)')
  // ['a/file.txt']

  Thanks @ AgentEnder for the issue (#357).

  🚀 Improvements

  This release includes performance improvements for the asynchronous method. For this method we now use an asynchronous directory traversal interface instead of using a streaming interface. This gives up to 15% acceleration for medium and large directories. The result depends a lot on hardware.

  You can find the benchmark results for this release in CI here.

  Here are a few of measurements on my laptop:

  ===> Benchmark pattern "*" with 100 launches (regression, async)
  ===> Max stdev: 7 | Retries: 3 | Options: {}

  Name Time, ms Time stdev, % Memory, MB Memory stdev, % Entries Errors Retries
  --------------------- -------- ------------- ---------- --------------- ------- ------ -------
  fast-glob-current.js 4.390 0.252 6.253 0.015 4 0 1
  fast-glob-previous.js 5.653 0.633 6.051 0.056 4 0 1

  ===> Benchmark pattern "**" with 100 launches (regression, async)
  ===> Max stdev: 7 | Retries: 3 | Options: {}

  Name Time, ms Time stdev, % Memory, MB Memory stdev, % Entries Errors Retries
  --------------------- -------- ------------- ---------- --------------- ------- ------ -------
  fast-glob-current.js 34.587 1.287 10.654 0.607 11835 0 1
  fast-glob-previous.js 41.972 2.086 10.236 1.224 11835 0 1

  
  


• 
  3.2.11 - 2022-01-14
  

  Full Changelog: 3.2.10...3.2.11

  🐛 Bug fixes

  Yeap, this is another release aimed at fixing problems with detecting brace expansions in patterns. This time, patterns like abc/{a.txt,b.js} was not marked as a dynamic pattern. So, now the regex has been rewritten to a generalized solution as a function to avoid future problems due to the complexity of the regular expression.

  Thanks @ MurzNN for the report of this problem (#351).

• 3.2.10 - 2022-01-09
  

  Full Changelog: 3.2.9...3.2.10

  🐛 Bug fixes

  • Fixed a regression in 3.2.8 when the {a,b,c} pattern no longer considered a dynamic pattern (thanks @ amitdahan, #347).

  🥇 New Contributors

  • @ amitdahan made their first contribution in #348
• 3.2.9 - 2022-01-07
  

  Full Changelog: 3.2.8...3.2.9

  🐛 Bug fixes

  • Fixed a regression in 3.2.8 with invalid regular expression on older node.js versions (#345).
• 3.2.8 - 2022-01-07
  

  Full Changelog: 3.2.7...3.2.8

  🐛 Bug fixes

  Fix directory matching with trailing slashes (#290)

  Thanks @ Trott for investigating the problem and the detailed description.

  Previously the src/*/ pattern did not work as expected (like src/*).

  Double-slash in the middle of the pattern is not collapsed (#330)

  Starting from this release, patterns like src//* will work like similar patterns without duplicate slashes. This was done for continuity with other solutions (glob, ls src//*, python, golang, …).

  Adjust inefficient regular expressions (#336, #342, #344)

  Thanks @ Trott for fixing bugs and @ XhmikosR for adding the CodeQL action to CI pipeline.

  📖 Documentation

  • Some documentation improvements (#327, thanks @ MarcelloTheArcane).

  ⚙️ Infrastructure

  • The CodeQL action has been added to CI pipeline (#338, thanks @ XhmikosR).

  🥇 New Contributors

  • @ MarcelloTheArcane made their first contribution in #327
  • @ Trott made their first contribution in #336
  • @ XhmikosR made their first contribution in #338
• 3.2.7 - 2021-07-08
  

  🐛 Bug fixes

  The previous release (3.2.6) introduced a regression, which makes negative patterns were not applied to patterns outside the current directory.

  This release fixes the issue.

• 3.2.6 - 2021-06-27
• 3.2.5 - 2021-01-17
• 3.2.4 - 2020-06-16
• 3.2.3 - 2020-06-15
• 3.2.2 - 2020-02-21
• 3.2.1 - 2020-02-20
• 3.2.1-beta.1 - 2020-02-20
• 3.2.1-beta.0 - 2020-02-20
• 3.2.0 - 2020-02-15
• 3.2.0-beta.2 - 2020-02-09
• 3.2.0-beta - 2020-02-04
• 3.1.1 - 2019-12-01
• 3.1.0 - 2019-10-06
• 3.0.4 - 2019-07-05
• 3.0.3 - 2019-06-27
• 3.0.2 - 2019-06-23
• 3.0.1 - 2019-06-17
• 3.0.0 - 2019-06-16
• 2.2.7 - 2019-05-18
• 2.2.6 - 2019-01-07
• 2.2.5 - 2019-01-07
• 2.2.4 - 2018-11-11
• 2.2.3 - 2018-10-02
• 2.2.2 - 2018-05-15
• 2.2.1 - 2018-04-22

from fast-glob GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled resource consumption

[Omrisnyk]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)