[Snyk] Security upgrade del from 5.1.0 to 8.0.0

[cc-prodsec]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-MINIMATCH-15353389	828

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.

[cc-prodsec]

This is a major version upgrade for del from v5.1.0 to v8.0.0, which includes several significant breaking changes requiring code and environment updates.

Key Breaking Changes:

• ESM and Import Syntax: The package is now pure ESM. The import method has changed from a default export to named exports.

  • Previous (CommonJS): const del = require('del');
  • New (ESM): import { deleteAsync, deleteSync } from 'del';

• Node.js Requirement: The minimum required Node.js version has been increased to v18.

• Behavioral Changes (since v6.0.0):

  • The force option is now required to delete the current working directory.
  • In the onProgress callback, the percent value is now a float between 0 and 1, instead of an integer from 0 to 100.

Recommendation:
Due to the mandatory changes in import syntax and the switch to pure ESM, developers must update their code to use the new named exports (deleteAsync, deleteSync). Additionally, ensure your environment meets the new Node.js v18 requirement. Test thoroughly after upgrading to account for the behavioral changes.

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.

[cc-prodsec]

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

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.