[Snyk] Fix for 1 vulnerabilities

[AH7]

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

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650	721

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[AH7]

This upgrade includes multiple major versions with significant breaking changes, particularly for glob and rimraf. These packages have moved to Promise-based APIs, require modern Node.js versions, and have changed how they handle file paths and module imports. Developer action is required to adapt to these new APIs.

Top 3 Most Impactful Upgrades

1. glob 7.2.3 → 12.0.0: HIGH RISK

This is a complete rewrite with major breaking changes. Code using version 7 will not work without modification.

• Asynchronous API: The API is now Promise-based. Callback patterns are no longer supported.
• Module Imports: The package now only provides named exports; there is no default export.
• Path Separators: Backslashes (\) are now treated exclusively as escape characters. All glob patterns must use forward slashes (/) as path separators, even on Windows.
• Node.js Requirement: Requires Node.js v16 or higher.
• Removed Options: Many options from v7, such as silent, strict, nonull, and nosort, have been removed.

Recommendation: Code using glob must be refactored to use async/await or Promises, updated to use named imports, and all glob patterns must be verified to use forward slashes.

2. rimraf 2.7.1 → 6.1.1: HIGH RISK

This upgrade introduces several critical breaking changes across major versions.

• Glob Support is Now Opt-In: In v2, glob patterns were processed by default. Starting with v4, glob support was removed and later reintroduced as an opt-in feature. You must now explicitly enable it by setting the glob: true option or using the --glob flag in the CLI. This is a critical change that could cause scripts to fail silently by not deleting the intended files.
• Asynchronous API: The API is now Promise-based instead of using callbacks.
• Module Imports: Version 5 removed the default export, requiring named imports (e.g., import { rimraf } from 'rimraf').
• Node.js Requirement: Requires Node.js v20 or higher.

Recommendation: Review all rimraf calls. Enable the glob option where pattern matching is needed and refactor the code to use Promises and named imports.

3. fs-extra 0.30.0 → 1.0.0: MEDIUM RISK

This upgrade to the first stable major version introduces a key breaking change.

• Removed Functionality: The filter option for copy() and copySync() no longer accepts a RegExp. This was officially deprecated in v1.0.0 and will break any code that relied on it.

Recommendation:

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.