[Snyk] Security upgrade del from 3.0.0 to 8.0.0

[rvu-snyk]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Infinite loop SNYK-JS-BRACEEXPANSION-15789759	641

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.

[rvu-snyk]

This is a major version upgrade from v3 to v8, introducing significant breaking changes that require code modifications and a modern Node.js environment.

Key Breaking Changes:

• Node.js Requirement: The minimum required Node.js version has been increased to v18.0.0. The previous version, v3.0.0, was compatible with much older Node.js versions.
• ESM Module: The package is now a pure ESM (ECMAScript Module). It can no longer be imported using require(). You must use import and be in an ESM-supported environment.
• API Change (Named Exports): The package has moved from a default export to named exports. This requires changing how the function is imported and called.
  • Before (v3): const del = require('del'); await del(['file.js']);
  • After (v8): import { deleteAsync } from 'del'; await deleteAsync(['file.js']);
• Path Separators: Paths with backward-slashes are no longer supported. This is a breaking change for Windows environments. Paths should be normalized to use forward-slashes, for example by using path.posix.join().

Recommendation:
This upgrade requires significant code changes. Developers must update their import statements to use ESM and the new named exports (deleteAsync and deleteSync). Additionally, ensure your project is running on Node.js v18 or later and that all file paths use forward-slashes.

Source: GitHub Releases

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